| 2.1 |
Approval of the agenda |
|
| R2-2501701 |
Agenda for RAN2#129bis |
Chairman |
| 2.2 |
Approval of the report of the previous meeting |
|
| R2-2501702 |
RAN2#129 Meeting Report |
MCC |
| 2.5 |
Others |
|
| R2-2501703 |
RAN2 Handbook |
MCC |
| R2-2501885 |
Discussion on Git-based specification handling approach |
OPPO |
| R2-2502174 |
On specification file formats and workflows |
Apple |
| R2-2502548 |
Further aspects on improvements to specification handling |
Ericsson |
| 4.1 |
EUTRA corrections Rel-17 and earlier |
|
| R2-2502330 |
Clarification on A4 A5 ReportOnLeave |
ZTE Corporation, Sanechips |
| R2-2502331 |
Introducing UE capability for A4 A5 ReportOnLeave |
ZTE Corporation, Sanechips |
| R2-2502332 |
Introducing UE capability for A4 A5 ReportOnLeave |
ZTE Corporation, Sanechips |
| R2-2502333 |
Introducing UE capability for A4 A5 ReportOnLeave |
ZTE Corporation, Sanechips |
| R2-2502334 |
Introducing UE capability for A4 A5 ReportOnLeave |
ZTE Corporation, Sanechips |
| R2-2502528 |
Correction on timeUntilReconnection in RLF report |
ZTE Corporation, Sanechips |
| R2-2502529 |
Correction on timeUntilReconnection in RLF report |
ZTE Corporation, Sanechips |
| R2-2502561 |
Correction to explicit indication of epoch in SIB31 |
Nordic Semiconductor ASA |
| R2-2502836 |
Correction on deprioritisationReq delete |
Google |
| R2-2503102 |
Correction on timeUntilReconnection in RLF report |
ZTE Corporation, Sanechips |
| R2-2503103 |
Correction on timeUntilReconnection in RLF report |
ZTE Corporation, Sanechips |
| R2-2503116 |
Correction on timeUntilReconnection in RLF report |
ZTE Corporation, Xiaomi, Sanechips |
| 5.1.1 |
Stage 2 and Organisational |
|
| R2-2502473 |
Corrections on DCP |
Huawei, HiSilicon, Nokia (Rapporteur) |
| R2-2502474 |
Corrections on DCP |
Huawei, HiSilicon, Nokia (Rapporteur) |
| R2-2502475 |
Corrections on DCP |
Huawei, HiSilicon, Nokia (Rapporteur) |
| 5.1.2.1 |
MAC |
|
| R2-2502992 |
Clarification on the power ramping offset for 2-step RACH switching to 4-step RACH |
OPPO |
| R2-2502993 |
Clarification on the power ramping offset for 2-step RACH switching to 4-step RACH |
OPPO |
| R2-2502994 |
Clarification on the power ramping offset for 2-step RACH switching to 4-step RACH |
OPPO |
| 5.1.3.1 |
NR RRC |
|
| R2-2501906 |
Correction on Initiation of NR SCG failure information |
CATT |
| R2-2501907 |
Correction on Initiation of NR SCG failure information |
CATT |
| R2-2501908 |
Correction on Initiation of NR SCG failure information |
CATT |
| R2-2502271 |
Correction to nrofCandidates-CI for DCI format 2_4 |
Huawei, HiSilicon |
| R2-2502272 |
Correction to nrofCandidates-CI for DCI format 2_4 |
Huawei, HiSilicon |
| R2-2502273 |
Correction to nrofCandidates-CI for DCI format 2_4 |
Huawei, HiSilicon |
| R2-2502344 |
Correction on number of NZP CSI-RS resources |
Ericsson |
| R2-2502389 |
Correction on number of NZP CSI-RS resources |
Ericsson |
| R2-2502390 |
Correction on number of NZP CSI-RS resources |
Ericsson |
| R2-2502391 |
Correction on number of NZP CSI-RS resources |
Ericsson |
| R2-2502884 |
Issues on PUCCH Spatial Relation Info Configuration |
ZTE, Samsung |
| 5.1.3.2 |
UE capabilities |
|
| R2-2502505 |
Type clarification for interBandMRDC-WithOverlapDL-Bands-r16 |
Apple, Huawei, HiSilicon, xiaomi |
| R2-2502506 |
Type clarification for interBandMRDC-WithOverlapDL-Bands-r16 |
Apple, Huawei, HiSilicon, xiaomi |
| R2-2502507 |
Type clarification for interBandMRDC-WithOverlapDL-Bands-r16 |
Apple, Huawei, HiSilicon, xiaomi |
| R2-2502631 |
Correction to pdsch-256QAM-FR1 for IAB-MT |
Nokia |
| R2-2502632 |
Correction to pdsch-256QAM-FR1 for IAB-MT |
Nokia |
| R2-2502633 |
Correction to pdsch-256QAM-FR1 for IAB-MT |
Nokia |
| R2-2502865 |
Consideration on Introduction of SRS Capability Reporting for SRS-only cell |
ZTE Corporation |
| R2-2502891 |
Correction on SRS capability reporting |
Huawei, HiSilicon, Ericsson, OPPO |
| R2-2502892 |
Correction on SRS capability reporting |
Huawei, HiSilicon, Ericsson, OPPO |
| R2-2502893 |
Correction on SRS capability reporting |
Huawei, HiSilicon, Ericsson, OPPO |
| R2-2502894 |
Correction on SRS capability reporting |
Huawei, HiSilicon, Ericsson, OPPO |
| R2-2502895 |
Correction on SRS capability reporting |
Huawei, HiSilicon, Ericsson, OPPO |
| R2-2502896 |
Correction on SRS capability reporting |
Huawei, HiSilicon, Ericsson, OPPO |
| R2-2502897 |
Correction on SRS capability reporting |
Huawei, HiSilicon, Ericsson, OPPO |
| R2-2502898 |
Correction on SRS capability reporting |
Huawei, HiSilicon, Ericsson, OPPO |
| R2-2502991 |
Consideration on Introduction of SRS Capability Reporting for SRS-only cell |
ZTE Corporation |
| R2-2503104 |
Correction on SRS capability reporting |
Huawei, HiSilicon, Ericsson, OPPO |
| R2-2503105 |
Correction on SRS capability reporting |
Huawei, HiSilicon, Ericsson, OPPO |
| R2-2503106 |
Correction on SRS capability reporting |
Huawei, HiSilicon, Ericsson, OPPO |
| R2-2503107 |
Correction on SRS capability reporting |
Huawei, HiSilicon, Ericsson, OPPO |
| R2-2503108 |
Correction on SRS capability reporting |
Huawei, HiSilicon, Ericsson, OPPO |
| R2-2503109 |
Correction on SRS capability reporting |
Huawei, HiSilicon, Ericsson, OPPO |
| R2-2503110 |
Correction on SRS capability reporting |
Huawei, HiSilicon, Ericsson, OPPO |
| R2-2503111 |
Correction on SRS capability reporting |
Huawei, HiSilicon, Ericsson, OPPO |
| 5.1.3.3 |
Other |
|
| R2-2502011 |
Clarification on usage of q-RxLevMinSUL |
Qualcomm Incorporated (Rapporteur) |
| R2-2502012 |
Clarification on usage of q-RxLevMinSUL |
Qualcomm Incorporated (Rapporteur) |
| R2-2502013 |
Clarification on usage of q-RxLevMinSUL |
Qualcomm Incorporated (Rapporteur) |
| R2-2502015 |
Clarification on usage of q-RxLevMinSUL |
Qualcomm Incorporated (Rapporteur) |
| R2-2502404 |
Correction to Immediate MDT measurements |
Nokia |
| R2-2502405 |
Correction to Immediate MDT measurements |
Nokia |
| R2-2502406 |
Correction to Immediate MDT measurements |
Nokia |
| 5.3 |
NR Positioning Support |
|
| R2-2502922 |
Correction for equalIntegerAmbiguity Request from UE |
Ericsson |
| R2-2502923 |
Correction for equalIntegerAmbiguity Request from UE |
Ericsson |
| R2-2502924 |
Correction for equalIntegerAmbiguity Request from UE |
Ericsson |
| 6.1.1 |
Stage 2 and Organisational |
|
| R2-2501704 |
LS on stage 1 requirements for the support for PWS over satellite NGRAN in Rel-17 (C1-250715; contact: Qualcomm) |
CT1 |
| R2-2502441 |
Correction on cell type specific cell reselection prioritisation [NR_HSDN] |
Huawei, HiSilicon, Nokia, Qualcomm, CMCC, Xiaomi, CATT, Apple |
| R2-2502442 |
Correction on cell type specific cell reselection prioritisation [NR_HSDN] |
Huawei, HiSilicon, Nokia, Qualcomm, CMCC, Xiaomi, CATT, Apple |
| 6.1.2 |
User Plane corrections |
|
| R2-2502305 |
Correction to MAC on IUC |
Ericsson, Apple, ZTE Corporation, Sanechips |
| R2-2502306 |
Correction to MAC on IUC |
Ericsson, Apple, ZTE Corporation, Sanechips |
| R2-2502614 |
Correction on IAB related MAC CEs |
ZTE Corporation, Samsung, Sanechips |
| R2-2502615 |
Correction on IAB related MAC CEs |
ZTE Corporation, Samsung, Sanechips |
| R2-2502654 |
Corrections on Power saving features in NTN |
Qualcomm Incorporated |
| 6.1.3 |
Control Plane corrections |
|
| R2-2501716 |
LS on Slot aggregation configuration with multi-PUSCH (R1-2501593; contact: Nokia) |
RAN1 |
| R2-2502920 |
Slot aggregation configuration with multi-PUSCH |
Nokia |
| R2-2502921 |
Slot aggregation configuration with multi-PUSCH |
Nokia |
| 6.1.3.1 |
NR RRC |
|
| R2-2502049 |
CR on the usage of msg3-transmitPrecoder |
CATT, Huawei, HiSilicon |
| R2-2502050 |
CR on the usage of msg3-transmitPrecoder |
CATT, Huawei, HiSilicon |
| R2-2502051 |
CR on the usage of RACH parameters in the case of fallbackRAR |
CATT, Huawei, HiSilicon |
| R2-2502052 |
CR on the usage of RACH parameters in the case of fallbackRAR |
CATT, Huawei, HiSilicon |
| R2-2502140 |
Discussion on UE Radio Capability for Paging Information |
CATT |
| R2-2502249 |
Correction on carrier frequency information in RRCConnectionRelease. |
CATT, Qualcomm Incorporated |
| R2-2502250 |
Correction on carrier frequency information in RRCConnectionRelease. |
CATT, Qualcomm Incorporated |
| R2-2502335 |
Correction on SCS and CP configuration in RedCap-specific initial BWP |
ZTE Corporation, Sanechips, Vivo, Ericsson, MediaTek Inc, Qualcomm Incorporated, OPPO, Samsung |
| R2-2502336 |
Correction on SCS and CP configuration in RedCap-specific initial BWP |
ZTE Corporation, Sanechips, Vivo, Ericsson, MediaTek Inc, Qualcomm Incorporated, OPPO, Samsung |
| R2-2502415 |
Correction on PUCCH spatial relation Activation/Deactivation for multiple TRP PUCCH repetition MAC CE |
ZTE Corporation, Samsung |
| R2-2502416 |
Correction on PUCCH spatial relation Activation/Deactivation for multiple TRP PUCCH repetition MAC CE |
ZTE Corporation, Samsung |
| R2-2502472 |
Discussion on the issue of UE radio paging capability loss |
Huawei, HiSilicon |
| R2-2502519 |
Corrections to location-based measurement |
ZTE Corporation, Ericsson, CATT, Sanechips |
| R2-2502573 |
Miscellaneous non-controversial corrections Set XXV |
Ericsson |
| R2-2502754 |
Correction on rsrp-ThresholdSSB-r17 in TS 38.331(R17) |
Huawei, HiSilicon |
| R2-2502755 |
Correction on rsrp-ThresholdSSB-r17 in TS 38.331(R18) |
Huawei, HiSilicon |
| R2-2502940 |
Correction on CFRA for SCG activation |
Huawei, HiSilicon |
| R2-2502941 |
Correction on CFRA for SCG activation |
Huawei, HiSilicon |
| R2-2503112 |
CR on the usage of msg3-transmitPrecoder |
CATT, Huawei, HiSilicon |
| R2-2503113 |
CR on the usage of msg3-transmitPrecoder |
CATT, Huawei, HiSilicon |
| R2-2503114 |
Correction on rsrp-ThresholdSSB-r17 in TS 38.331(R17) |
Huawei, HiSilicon |
| R2-2503115 |
Correction on rsrp-ThresholdSSB-r17 in TS 38.331(R18) |
Huawei, HiSilicon |
| 6.1.3.2 |
UE capabilities |
|
| R2-2501884 |
Discussion on Paging Capability Issue |
OPPO |
| R2-2501953 |
Discussion on UE capabilities to be included in UE Radio Paging Information |
ZTE Corporation, Sanechips |
| R2-2502172 |
Discussion on capability mis-match issue for LP-WUS, PEI, (e)RedCap, 2Rx XR, NTN, inactiveStatePO-Determination |
vivo |
| R2-2502520 |
Corrections to location-based measurement initiation |
ZTE Corporation, Ericsson, CATT, Sanechips |
| R2-2502521 |
Corrections to location-based measurement initiation |
ZTE Corporation, Ericsson, CATT, Sanechips |
| R2-2502837 |
Correction to ul-GapFR2-r17 |
Huawei, HiSilicon, Apple, Nokia, Nokia Shanghai Bell, Ericsson, MediaTek Inc. |
| R2-2502838 |
Correction to ul-GapFR2-r17 |
Huawei, HiSilicon, Apple, Nokia, Nokia Shanghai Bell, Ericsson, MediaTek Inc. |
| 6.1.3.3 |
Other |
|
| R2-2501752 |
Reply LS on emergency call back and paging (S2-2502427; contact: ZTE) |
SA2 |
| R2-2501975 |
On emergency services and eDRX |
MediaTek Inc. |
| R2-2502337 |
On eDRX operation with emergency PDU session |
ZTE Corporation, Sanechips |
| R2-2502338 |
Correction on eDRX configuration in RRC_INACTIVE |
ZTE Corporation, Sanechips |
| R2-2502339 |
Correction on eDRX configuration in RRC_INACTIVE |
ZTE Corporation, Sanechips |
| R2-2502504 |
Discussion on emergency services and eDRX |
Nokia, Huawei, HiSilicon |
| R2-2502909 |
Emergency callback and paging |
Ericsson |
| R2-2502955 |
(e)DRX usage clarification for UEs with emergency PDU Sessions |
Nokia, Huawei, HiSilicon |
| R2-2502956 |
(e)DRX usage clarification for UEs with emergency PDU Sessions |
Nokia, Huawei, HiSilicon |
| R2-2502962 |
(e)DRX usage clarification for UEs with emergency PDU Sessions |
Nokia, Huawei, HiSilicon |
| R2-2502963 |
(e)DRX usage clarification for UEs with emergency PDU Sessions |
Nokia, Huawei, HiSilicon |
| 7.0.1 |
UE Capabilities |
|
| R2-2501706 |
LS on Rel-18 RAN1 UE features list for NR after RAN1#120 (R1-2501390; contact: NTT DOCOMO, AT&T) |
RAN1 |
| 7.0.2 |
Rel-18 corrections |
|
| R2-2502574 |
Miscellaneous non-controversial corrections Set XXV |
Ericsson |
| R2-2503184 |
Miscellaneous non-controversial corrections Set XXV |
Ericsson |
| 7.0.2.1 |
RACH-less HO |
|
| R2-2501772 |
Discussion on RACH-less HO Use Case Capturing in Stage-2 |
vivo, CATT, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| R2-2502090 |
Rapporteur CR for RACH-less HO and LTM [RACH-lessHO] |
Huawei, HiSilicon, CATT, Nokia, Qualcomm, Samsung |
| R2-2502532 |
Support of inter-gNB scenarios for RACH-less handover |
Ericsson |
| R2-2502605 |
Correction on RACH-less HO in NR-NTN |
vivo, Ericsson, Nokia, Nokia Shanghai Bell, ZTE Corporation, Sanechips, THALES, Aalyria, Samsung |
| R2-2503167 |
Correction on RACH-less HO Use Case |
vivo, Nokia, Nokia Shanghai Bell, Ericsson, Samsung |
| 7.0.2.10 |
Network energy savings for NR |
|
| R2-2501740 |
LS on neighboring cell measurement for Rel-18 SSB-less (R4-2502694; contact: ZTE) |
RAN4 |
| R2-2501952 |
Consideration on servingCellMO for SSB-less Scell |
ZTE Corporation, Sanechips |
| R2-2501985 |
Correction for cell barring for NES CellDTX-DRX UEs |
Huawei, HiSilicon |
| R2-2502417 |
Correction on Semi-Persistent CSI Report SubConfiguration Activation/Deactivation MAC CE |
ZTE, Apple, Qualcomm Incorporated |
| R2-2502843 |
Discussion on servingCellMO for SSB-less Scell |
Huawei, HiSilicon, Apple, Qualcomm Incorporated, MediaTek Inc. |
| R2-2502919 |
SSBLess handling |
Nokia |
| R2-2502998 |
Correction for cell barring for NES CellDTX-DRX UEs |
Huawei, HiSilicon |
| R2-2503173 |
Summary of offline discussion on servingCellMO for SSB-less Scell |
ZTE Corporation, Sanechips |
| 7.0.2.11 |
Further enhancement of data collection for SON MDT in NR and EN-DC |
|
| R2-2501909 |
Corrections on SPR configuration |
CATT |
| R2-2502407 |
Updating references to TS 28.558 from TS 28.552 |
Nokia |
| R2-2502530 |
Correction on timeSinceSHR in SHR report |
ZTE Corporation, Sanechips |
| R2-2502645 |
Correction on ra-InformationCommon logging in RLF-Report SHR and SPR |
Ericsson |
| R2-2502798 |
Correction on SON for NPN in TS 38.300 |
Huawei, HiSilicon, CATT, Samsung, ZTE, CMCC |
| R2-2502844 |
Correction on logging intendedSIBs |
Samsung |
| 7.0.2.12 |
Dual Transmission/Reception (Tx/Rx) Multi-SIM for NR |
|
| R2-2502868 |
Clarification on the MUSIM Gap and Measurement Gap Collision |
ZTE Corporation |
| R2-2503163 |
LS on Collision between MUSIM Gap and Measurement Gap |
RAN2 |
| 7.0.2.13 |
NR MIMO evolution |
|
| R2-2501712 |
LS on RRC parameter for PRACH transmission in 2TA (R1-2501540; contact: CATT) |
RAN1 |
| R2-2501719 |
Reply LS on differentiation of sDCI mTRP, mDCI mTRP and sTRP (R1- 2501611; contact: CATT) |
RAN1 |
| R2-2501723 |
Reply LS on UL 8Tx (R1-2501636; contact: Samsung) |
RAN1 |
| R2-2502105 |
Corrections on simultaneousU-TCI-UpdateListx and RACH-ConfigTwoTA |
CATT |
| R2-2502810 |
Discussion on supporting 8Tx |
ASUSTeK |
| R2-2502811 |
Correction on supporting 8Tx in MAC specification |
ASUSTeK, Samsung, ZTE |
| R2-2502812 |
Stage-2 Correction on UL 8Tx |
ASUSTeK |
| R2-2502835 |
Correction on supporting 8Tx in MAC specification |
ASUSTeK, Samsung, ZTE |
| R2-2502855 |
Correction to 306 on PMI subband R value |
Ericsson |
| R2-2502987 |
Correction for UE capability on DMRS port |
Huawei, HiSilicon |
| R2-2503034 |
Correction on supporting 8Tx in MAC specification |
ASUSTeK, Samsung, ZTE |
| 7.0.2.15 |
Enhancement on NR QoE management and optimizations for diverse services |
|
| R2-2501729 |
Reply LS on MBS Communication Service Type (R3-250858; contact: ZTE) |
RAN3 |
| 7.0.2.16 |
XR Enhancements for NR |
|
| R2-2502092 |
Discussion on issues with retx-less CG |
Huawei, HiSIlicon, Apple, Futurewei, Qualcomm |
| R2-2502297 |
Discussing on issues on DSR and proposed TP to PDCP |
Xiaomi Communications |
| R2-2502857 |
Corrections on PDCP SN Gap Reporting |
Samsung |
| R2-2502933 |
DSR inclusion |
Ericsson |
| R2-2502999 |
Correction to UE capability for retx-less CG |
Huawei, HiSilicon, Apple, Futurewei, Qualcomm |
| R2-2503000 |
Correction to RRC spec for retx-less CG |
Huawei, HiSilicon, Apple, Futurewei, Qualcomm |
| 7.0.2.17 |
NR NTN enhancements |
|
| R2-2501717 |
Reply LS on soft satellite switch with re-sync (R1-2501606; contact: Huawei) |
RAN1 |
| R2-2501727 |
Reply LS on inter-gNB RACH-less HO in NTN (R3-250762; contact: Nokia) |
RAN3 |
| R2-2501741 |
reply LS on soft satellite switch with re-sync (R4-2502701; contact: Huawei) |
RAN4 |
| R2-2501747 |
Reply LS to RAN2 on UE capabilities for FR2-NTN (R4-2503039; contact: vivo) |
RAN4 |
| R2-2501771 |
Discussion on RAN1 and RAN4 Reply LS on Soft Satellite Switch with Re-sync |
vivo |
| R2-2501782 |
Correction on NTN in FR2-NTN bands |
vivo, ZTE Corporation, Ericsson, Sanechips |
| R2-2502009 |
Correction to RACH-less handover for NTN |
Xiaomi |
| R2-2502294 |
Discussion on the reply LS from RAN1/RAN4 on soft satellite switch |
CATT |
| R2-2502327 |
Discussion on the satellite switch with sync |
OPPO |
| R2-2502523 |
Discussion on ssb-TimeOffset for soft satellite switch with resync |
ZTE Corporation, Sanechips |
| R2-2502539 |
Discussion on the reply LSs on the soft satellite switch with resynchronization |
Xiaomi |
| R2-2502550 |
Further Considerations on SSBs from Source and Target Satellite in Soft Switching with Resynchronization |
Nokia, Nokia Shanghai Bell |
| R2-2502653 |
Way forward for soft satellite switch with resync |
Qualcomm Incorporated |
| R2-2502669 |
Correction to Rel-18 NR NTN CHO with only location/time-based trigger |
Samsung |
| R2-2502670 |
Correction to Rel-18 NR NTN CHO with only location/time-based trigger |
Samsung |
| R2-2502681 |
LS response to RAN1 and RAN4 for soft satellite switch with re-sync |
Ericsson |
| R2-2502740 |
Discussion on LS from RAN1,RAN4 on soft satellite switch with re-sync |
CMCC |
| R2-2502842 |
Discussion on satellite switch with resync |
Huawei, HiSilicon |
| R2-2503051 |
[Draft] LS on soft satellite switch with re-sync |
Huawei |
| R2-2503052 |
Clarification on ssb-TimeOffset |
Huawei |
| R2-2503065 |
Reply LS on soft satellite switch with re-sync |
RAN2 |
| R2-2503066 |
Clarification on ssb-TimeOffset |
Huawei |
| R2-2503069 |
Reply LS on soft satellite switch with re-sync |
RAN2 |
| 7.0.2.18 |
IoT NTN enhancements |
|
| R2-2501726 |
Reply LS on UE Location Information for NB-IoT NTN (R3-250761; contact Qualcomm) |
RAN3 |
| R2-2501968 |
Correction on SIB33 reception in RRC_CONNECTED |
Huawei, HiSilicon |
| R2-2502522 |
Corrections to location-based measurement |
ZTE Corporation, Ericsson, CATT, Sanechips |
| R2-2502687 |
Correction on release procedures when HARQ feedback is not configured |
Samsung |
| R2-2503061 |
Correction on SIB33 reception in RRC_CONNECTED |
Huawei, HiSilicon |
| R2-2503062 |
Corrections to location-based measurement |
ZTE Corporation, Ericsson, CATT, Sanechips |
| 7.0.2.19 |
Enhanced NR Sidelink Relay |
|
| R2-2502184 |
Correction to PC5 RLC Channel Release |
Apple, ASUSTek |
| R2-2502779 |
Discussion on prerequisite of Rel-17/18 SL relay capability |
Samsung, OPPO, Xiaomi, Huawei, HiSilicon |
| R2-2502813 |
Correction on terminology of local ID pair list |
ASUSTeK |
| R2-2502814 |
Correction on mapping bi-directional E2E sidelink DRB to two AM RLC entities for L2 U2U Relay |
ASUSTeK |
| R2-2502936 |
Correction on sidelink relay RRC specification |
ZTE Corporation, Sanechips |
| R2-2503081 |
Correction to PC5 RLC Channel Release |
Apple, ASUSTek |
| R2-2503082 |
Summary of offline discussion on the prerequisite of Rel-17/18 SL relay capability |
Samsung |
| R2-2503083 |
Correction on terminology of local ID pair list |
ASUSTeK |
| R2-2503084 |
Correction on sidelink relay RRC specification |
ZTE Corporation, Sanechips |
| 7.0.2.20 |
TEI18 |
|
| R2-2501746 |
LS on NR NB-IoT in-band operation (R4-2503035; contact: Ericsson) |
RAN4 |
| R2-2501773 |
Discussion on RAN4 LS on IoT NTN and NR NTN Inband Operation. |
vivo |
| R2-2502047 |
RAN2 impacts for NB-IoT operation as NR Inband |
Nokia , Nokia Shanghai Bells |
| R2-2502476 |
Correction on UE capability for SIB17bis |
Huawei, HiSilicon |
| R2-2502682 |
In-band operation for NB-IoT |
Ericsson |
| R2-2503053 |
Report of [AT129bis][302][TEI18] in-band operation for NB-IoT |
Ericsson |
| R2-2503054 |
Draft Reply on NR NB-IoT in-band operation |
Ericsson |
| R2-2503063 |
Report of [AT129bis][302][TEI18] In-band operation for NB-IoT (Ericsson) |
Ericsson |
| R2-2503064 |
Draft Reply on NR NB-IoT in-band operation |
Ericsson |
| 7.0.2.21 |
Others |
|
| R2-2502508 |
Type clarification for intraBandNR-CA-non-collocated-r18 |
Apple, Huawei, HiSilicon, xiaomi |
| 7.1.1 |
Organizational |
|
| R2-2501708 |
Reply LS on co-existence of SL-CA and SL PRS transmission/reception in Dedicated SL-PRS resource pool (R1-2501479; contact: vivo) |
RAN1 |
| R2-2502973 |
Correction on NW restriction for dedicated SL-PRS resource pool |
vivo, Ericsson |
| R2-2503079 |
Correction on NW restriction for dedicated SL-PRS resource pool |
vivo, Ericsson |
| 7.1.3 |
SLPP corrections |
|
| R2-2501896 |
Missing rate of change direction of azimuth/elevation for relative velocity |
Xiaomi, Qualcomm, CATT, Huawei, MediaTek Inc. |
| 7.1.4 |
LPP corrections |
|
| R2-2501852 |
Corrections on the descriptions of nr-PeriodicOrOneShotTimeWindow and nr-StartSFN-TimeWindow |
CATT, Qualcomm Incorporated |
| R2-2502274 |
Correction on the periodic AD of NR integrity service alert |
Huawei, HiSilicon |
| R2-2503080 |
Corrections on the descriptions of nr-PeriodicOrOneShotTimeWindow and nr-StartSFN-TimeWindow |
CATT, Qualcomm Incorporated |
| 7.1.5 |
RRC corrections |
|
| R2-2501793 |
Correction on condition-based IUC for shared SL-PRS resource pool |
vivo, Ericsson |
| R2-2502079 |
Correction on SL positioning UE capability |
Huawei, HiSilicon |
| R2-2502663 |
RRC Sidelink Positioning Correction |
Ericsson, vivo |
| R2-2502815 |
Correction on sl-PRS-ResourcePoolID for SL-PRS CG |
ASUSTeK |
| R2-2502888 |
Corrections on RRC connection resume procedure initiated by activation or configuration of positioning SRS |
CATT |
| R2-2502990 |
Correction on sl-PRS-ResourcePoolID for SL-PRS CG |
ASUSTeK, Ericsson |
| 7.1.6 |
MAC corrections |
|
| R2-2502078 |
Correction to UTW for positioning SRS frequency hopping |
Huawei, HiSilicon |
| R2-2502080 |
Correction on SRS hopping in positioning |
ZTE Corporation, Ericsson, CATT, Samsung, vivo, Xiaomi, Qualcomm, Lenovo |
| R2-2502081 |
Discussion and draft LS for startSFN in UTW |
ZTE Corporation |
| R2-2503087 |
LS on the startSFN parameter for positioning SRS with TX frequency hopping |
RAN2 |
| 7.2 |
Further NR mobility enhancements |
|
| R2-2501730 |
Reply LS on L3 measurement based LTM support over F1 (R3-250879; contact: Vodafone) |
RAN3 |
| R2-2501736 |
Reply LS on the fast RRC processing for LTM (R4-2420218; contact: Ericsson) |
RAN4 |
| R2-2501737 |
LS on UE capability for L1-RSRP measurement in LTM (R4-2502619; contact: vivo) |
RAN4 |
| R2-2501748 |
Reply LS on L3 measurement based LTM support over F1 (RP-250790; contact: Vodafone) |
RAN |
| R2-2501904 |
Handling of the default SRB configuration upon LTM execution |
CATT |
| R2-2501932 |
Correction on LTM UE Capability based on the RAN4 LS |
MediaTek Inc. |
| R2-2501976 |
Clarification on LTM cell switch failure recovery |
Google Korea LLC |
| R2-2502169 |
Discussion on indication from MAC to RRC layer in RACH-based LTM |
vivo |
| R2-2502170 |
Correction on UE capability for L1-RSRP measurement in LTM |
vivo, Ericsson, Xiaomi |
| R2-2502171 |
Correction on the maximum number of SSB rsources for L1 maeasurement without gaps in LTM |
vivo, Ericsson, Xiaomi |
| R2-2502533 |
Capability coordination for LTM |
Ericsson |
| R2-2502553 |
Remaining Rel-18 LTM Corrections |
Nokia |
| R2-2502600 |
Rel-18 LTM issues |
Ofinno, LLC |
| R2-2502942 |
Handling of PUCCH resources for L1 LTM reports at TAT expiry |
Huawei, HiSilicon |
| R2-2502943 |
MAC CR rapporteur summary |
Huawei, HiSilicon |
| R2-2502966 |
Discussion on eEMR/IMR and LTM L2 Reset/UE-based TA measurement |
Samsung Electronics Czech |
| R2-2502971 |
Handling of PUCCH resources for L1 LTM reports at TAT expiry |
Huawei, HiSilicon |
| R2-2502979 |
Summary of RRC proposals for FeMob |
Ericsson |
| R2-2503007 |
Corrections on eEMR/IMR and LTM L2 Reset/UE-based TA measurement |
Samsung |
| R2-2503008 |
Handling of the default SRB configuration upon LTM execution |
CATT |
| R2-2503009 |
Handling of PUCCH resources for L1 LTM reports at TAT expiry |
Huawei, HiSilicon |
| R2-2503016 |
Correction on UE capability for L1-RSRP measurement in LTM |
vivo, Ericsson, Xiaomi |
| R2-2503017 |
Correction on the maximum number of SSB rsources for L1 maeasurement without gaps in LTM |
vivo, Ericsson, Xiaomi |
| R2-2503018 |
Capability coordination for LTM |
Ericsson |
| R2-2503020 |
Corrections on eEMR/IMR and LTM L2 Reset/UE-based TA measurement |
Samsung |
| R2-2503021 |
Correction on the maximum number of SSB rsources for L1 maeasurement without gaps in LTM |
vivo, Ericsson, Xiaomi |
| 7.6 |
NR Sidelink evolution |
|
| R2-2501735 |
LS on AdditionalSpectrumEmission in NR SL Pre-configuration (R4-2418075; contact: LGE) |
RAN4 |
| R2-2502061 |
Discussion on resource re-selection in case of LBT failure on MCSt |
LG Electronics Inc. |
| R2-2502062 |
MAC correction on Release-18 Sidelink evolution |
LG Electronics Inc. |
| R2-2502185 |
Correction on MCSt Restriction for Resource Selection |
Apple |
| R2-2502322 |
Discussion on resource re-selection from SL LBT Failure indication |
Ericsson, Apple, Qualcomm Incorporated, vivo |
| R2-2502935 |
Correction on sidelink RRC specification |
ZTE Corporation, Sanechips, Ericsson |
| R2-2503010 |
Correction on sidelink RRC specification |
ZTE Corporation, Sanechips, Ericsson |
| R2-2503014 |
Summary of [AT129b][101][V2X/SL] Discuss multiple candidate options for SL resource (re)selection in MCSt (LG) |
LG Electronics Inc. |
| 7.8.1 |
RAN4 led items |
|
| R2-2501745 |
LS on clarification for intraBandNR-CA-non-collocated-r18 and interBandMRDC-WithOverlapDL-Bands-r16 (R4-2503033; contact: Apple, Huawei) |
RAN4 |
| R2-2502899 |
Clarification on capability for inter-frequency configuration for less than 5MHz |
Huawei, HiSilicon, Xiaomi, Samsung, Qualcomm Incorporated |
| R2-2503174 |
Clarification on capability for inter-frequency configuration for less than 5MHz |
Huawei, HiSilicon, Xiaomi, Samsung, Qualcomm Incorporated |
| 7.8.2 |
RAN1 led items |
|
| R2-2502270 |
Adding enabledDefaultBeamFormultiCellScheduling |
Huawei, HiSilicon, NTT DOCOMO INC. |
| R2-2502634 |
Correction to ULTxSwitchingBandPair-r18 |
Nokia |
| R2-2503164 |
Adding enabledDefaultBeamFormultiCellScheduling |
Huawei, HiSilicon, NTT DOCOMO INC., Samsung, Ericsson |
| 8.0 |
General |
|
| R2-2501707 |
LS on Rel-19 RAN1 UE features list for NR after RAN1#120 (R1-2501399; contact: NTT DOCOMO, AT&T) |
RAN1 |
| R2-2501724 |
LS on Rel-19 higher layers parameters list Post RAN1#120 (R1-2501644; contact: Ericsson) |
RAN1 |
| R2-2502093 |
Discussion on R19 ASN1 review |
Huawei, HiSilicon |
| R2-2502440 |
R19 ASN.1 identifier naming conventions and check list |
Huawei, HiSilicon |
| R2-2502643 |
RRC CR Guidelines |
Ericsson |
| R2-2502764 |
Report on [POST129][ASN.1] ASN.1 Review Process Improvements in Release 19 (Nokia) |
Nokia |
| R2-2502767 |
Rel-19 UE capability handling |
Xiaomi |
| R2-2503166 |
LS on Rel-19 higher layer parameter and UE Feature |
RAN2 |
| R2-2503171 |
RRC CR Guidelines |
Ericsson |
| R2-2503180 |
LS on Rel-19 higher layer parameter and UE Feature |
RAN2 |
| 8.1.1 |
Organizational |
|
| R2-2501710 |
Reply LS on LMF-based AI/ML Positioning for Case 2b (R1-2501523; contact: vivo) |
RAN1 |
| R2-2501711 |
Reply LS on LMF-based AI/ML Positioning for Case 3b (R1- 2501525; contact: Ericsson) |
RAN1 |
| R2-2501721 |
LS on AI/ML Positioning Case 3b (R1- 2501628; contact: Ericsson) |
RAN1 |
| R2-2501728 |
Reply LS on LMF-based AI/ML Positioning for case 3b (R3-250796; contact: ZTE) |
RAN3 |
| R2-2501759 |
Reply LS on AI/ML UE sided data collection (S5-250828; contact: Intel, NEC, Huawei) |
SA5 |
| R2-2501806 |
Introduction of AI for Air interface feature in 38300 |
vivo (Rapporteur) |
| R2-2501920 |
38.305 running CR for AIML Positioning |
CATT |
| R2-2502123 |
Running MAC CR for AI/ML for Air Interface |
Apple (Rapporteur) |
| R2-2502618 |
Running CR for AI/ML Positioning Accuracy Enhancements |
Qualcomm Incorporated |
| R2-2502661 |
LS on AI/ML Positioning Case 3b |
Ericsson |
| R2-2502793 |
Open issue list for running 37.320 CR for R19 AI for PHY |
Huawei, HiSilicon, Ericsson |
| R2-2502794 |
Draft LS on OAM-centric solution for NW-side data collection |
Huawei |
| R2-2502903 |
Draft RRC running CR for AIML PHY |
Ericsson |
| R2-2503162 |
LS on OAM-centric solution for NW-side data collection |
RAN2 |
| R2-2503168 |
LS on AI/ML UE sided data collection |
RAN2 |
| R2-2503170 |
LS on OAM-centric solution for NW-side data collection |
RAN2 |
| 8.1.2.2 |
LCM for UE-sided model for Beam Management use case |
|
| R2-2501783 |
Discussion on Applicable Functionality Reporting Option B for BM |
OPPO, Lenovo, ZTE Corporation, Apple, Huawei, HiSilicon, CATT, vivo, CMCC, NTT DOCOMO, Samsung, LG Electronics, Xiaomi, InterDigital |
| R2-2501784 |
LCM for UE-sided model for Beam Management use case |
OPPO |
| R2-2501807 |
Discussion on LCM for UE-sided model for Beam Management |
vivo |
| R2-2501921 |
Discussion on applicability reporting for BM use case |
CATT |
| R2-2501940 |
Unified Signaling Structure and Further consideration on applicability reporting |
Xiaomi |
| R2-2502020 |
LCM for UE-sided model for BM |
LG Electronics |
| R2-2502024 |
Discussion on LCM for UE-sided Model for Beam Management Use Case |
Fujitsu |
| R2-2502108 |
Further Discussion on LCM for UE-side Model for AI-BM |
MediaTek Inc. |
| R2-2502115 |
Discussion on LCM for UE-sided model for beam management |
Samsung |
| R2-2502124 |
Remaining issues on LCM procedure of UE-sided model for AI/ML based beam management |
Apple |
| R2-2502239 |
Further consideration on LCM for UE-sided model for BM use case |
China Telecom |
| R2-2502263 |
LCM for UE-sided Model for BM |
Google |
| R2-2502280 |
Discussion on signalling procedure of supporting applicability report Option B |
NEC |
| R2-2502290 |
On LCM for UE-sided Models for Beam Management |
Qualcomm Incorporated |
| R2-2502366 |
Left issues related to applicability report for AIML based BM |
Lenovo |
| R2-2502411 |
Continuous Discussion On LCM for UE-sided model |
ZTE Corporation |
| R2-2502421 |
Discussion on UE-sided model LCM for BM |
Transsion Holdings |
| R2-2502434 |
Discussion on LCM for UE-sided model for Beam Management |
Spreadtrum, UNISOC |
| R2-2502483 |
Some aspects for model monitoring on UE side |
Sony |
| R2-2502590 |
Discussion on LCM for UE-Side Model for Beam Management |
Futurewei Technologies |
| R2-2502599 |
Discussion on LCM for UE-sided model for Beam Management use case |
Huawei, HiSilicon |
| R2-2502636 |
On LCM for UE-sided Model for Beam Management Use Case |
SHARP Corporation |
| R2-2502637 |
LCM for UE-sided model for Beam Management use case |
InterDigital |
| R2-2502729 |
Discussion on LCM for UE-sided model for BM |
CMCC |
| R2-2502763 |
LCM for UE-side Beam Management |
Nokia |
| R2-2502772 |
LCM for UE-sided Model for Beam Management Use Case |
SHARP Corporation |
| R2-2502816 |
Discussion on LCM for UE-sided models |
ASUSTeK |
| R2-2502854 |
Remaining Issues on LCM for UE-sided model in Beam Management use case |
Kyocera |
| R2-2502902 |
LCM for UE-side models for beam management |
Ericsson |
| 8.1.2.3 |
LCM for Positioning use case |
|
| R2-2501787 |
LCM for Positioning use case |
OPPO |
| R2-2501808 |
Discussion on remaining issues of AI/ML enhanced positioning |
vivo |
| R2-2501827 |
Discussion on LCM for Positioning Use Case |
HONOR |
| R2-2501856 |
LCM for Positioning use case |
NEC |
| R2-2501922 |
Issues to address for AIML Positioning stage-2 |
CATT |
| R2-2501941 |
Discussion on the LCM for AI positioning case 1 |
Xiaomi |
| R2-2502025 |
Discussion on LCM for Positioning Use Case |
Fujitsu |
| R2-2502084 |
Discussion on LCM for positioning use case |
ZTE Corporation |
| R2-2502125 |
Remaining issues on LCM procedure of AI/ML based positioning |
Apple |
| R2-2502137 |
Discussion on LCM for POS use case |
Samsung |
| R2-2502240 |
Performance monitoring for positioning use case |
China Telecom |
| R2-2502367 |
LCM for AIML based positioning with UE-sided model |
Lenovo |
| R2-2502443 |
Association of measurements and ground truth labels for positioning use-cases |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2502617 |
LCM for positioning use case |
Qualcomm Incorporated |
| R2-2502638 |
LCM for Positioning use case |
InterDigital |
| R2-2502639 |
Reporting of applicability and inference configurations |
Nokia |
| R2-2502662 |
LCM For Positioning |
Ericsson |
| R2-2502697 |
Discussion on LCM for positioning |
CMCC |
| R2-2502758 |
Discussion on UE autonomous switching between AI/ML and non-AI/ML methods |
LG Electronics Inc. |
| R2-2502795 |
Discussion on LCM for Positioning use case |
Huawei, HiSilicon |
| R2-2502802 |
Discussion on Functionality-based LCM for Positioning Use Case |
CEWiT |
| 8.1.3 |
NW side data collection |
|
| R2-2501785 |
NW side data collection |
OPPO |
| R2-2501809 |
Discussion on NW side data collection |
vivo |
| R2-2501923 |
Consideration on NW side data collection |
CATT |
| R2-2501933 |
Discussion on NW side data collection |
Xiaomi |
| R2-2502004 |
Discussion on NW-side data collection |
NEC |
| R2-2502021 |
NW side data collection |
LG Electronics |
| R2-2502026 |
Discussion on NW side Data Collection |
Fujitsu |
| R2-2502109 |
Further Discussion on Network-Side Data Collection |
MediaTek Inc. |
| R2-2502114 |
Disuccsion on NW side data collection |
Samsung |
| R2-2502126 |
Remaining issues on NW-sided data collection |
Apple |
| R2-2502238 |
Discussion on NW side data collection |
China Telecom |
| R2-2502251 |
NW side data collection |
Interdigital Inc. |
| R2-2502264 |
Data Collection for NW-sided Model Training for BM |
Google |
| R2-2502291 |
On Network Side Data Collection |
Qualcomm Incorporated |
| R2-2502368 |
Data collection issues related to RAN3 and SA5 |
Lenovo |
| R2-2502369 |
Data collection for NW-sided model training |
Lenovo |
| R2-2502414 |
Further Discussion on NW Side Data Collection |
ZTE Corporation |
| R2-2502435 |
Discussion on NW side data collection |
Spreadtrum, UNISOC |
| R2-2502465 |
Discussion on NW-sided data collection for training |
Huawei, HiSilicon |
| R2-2502592 |
Discussion on Data Collection for NW-side Model Training |
Futurewei Technologies |
| R2-2502594 |
Data Collection for Training of network-side ML Models |
Nokia |
| R2-2502730 |
Discussion on NW side data collection |
CMCC |
| R2-2502817 |
Discussion on NW-sided data collection |
ASUSTeK |
| R2-2502832 |
Discussion on NW side data collection for positioning |
TCL |
| R2-2502904 |
NW-side data collection for beam management and positioning |
Ericsson |
| R2-2502908 |
Discussion on NW-Side AI/ML Data Logging Framework |
Rakuten Mobile, Inc |
| R2-2502937 |
Discussion on NW side data collection aspects |
Continental Automotive |
| 8.1.4 |
UE side data collection |
|
| R2-2501786 |
UE side data collection |
OPPO |
| R2-2501810 |
Discussion on UE side data collection |
vivo |
| R2-2501857 |
Analysis of solutions for UE side model data collection |
NEC |
| R2-2501924 |
Consideration on UE side data collection |
CATT |
| R2-2501934 |
Discussion on UE side data collection |
Xiaomi |
| R2-2501973 |
Discussion on UE-side data collection |
LG Electronics Inc. |
| R2-2501978 |
Performance metrics / KPI’s for UE sided data collection |
T-Mobile USA Inc. |
| R2-2502027 |
Discussion on Data Collection via UP Tunnel for UE-sided model |
Fujitsu |
| R2-2502110 |
Further Discussion on UE-side Data Collection |
MediaTek Inc. |
| R2-2502127 |
Further discussion on UE-side data collection |
Apple |
| R2-2502252 |
UE side data collection |
Interdigital Inc. |
| R2-2502292 |
On UE Side Data Collection |
Qualcomm Incorporated |
| R2-2502370 |
UE requests data collection for AI based positioning |
Lenovo |
| R2-2502413 |
Further Considerations on UE Side Data Collection |
ZTE Corporation |
| R2-2502593 |
Discussion on Data Collection for UE-side Model Training |
Futurewei Technologies |
| R2-2502595 |
Data collection for UE side models |
Nokia |
| R2-2502640 |
Data collection for positioning case 1 |
Nokia |
| R2-2502731 |
Discussion on UE side data collection |
CMCC,China Telecom |
| R2-2502752 |
On UE request of data collection configuration |
T-Mobile USA Inc., Nokia |
| R2-2502796 |
Discussion on UE-sided data collection for training |
Huawei, HiSilicon, OPPO, ZTE, NTT DoCoMo, China Unicom, CMCC, China Telecom, Apple, vivo |
| R2-2502818 |
Discussion on LCM for UE-sided data collection |
ASUSTeK |
| R2-2502906 |
Further Requirements for UE Side Data Collection |
Rakuten Mobile, Inc |
| R2-2502952 |
Remaining issues on UE-side data collection |
Ericsson |
| R2-2502961 |
UE side data collection |
Samsung R&D Institute UK |
| 8.1.5 |
Model transfer/delivery |
|
| R2-2501811 |
Discussion on signaling feasibility of OTA solutions |
vivo |
| R2-2501858 |
Signalling feasibility of dataset and parameter sharing |
NEC |
| R2-2501925 |
Signalling feasibility of AIML model transfer |
CATT |
| R2-2501939 |
Report of [POST129][029][AI Phy] Model transfer (Xiaomi/Ericsson) |
Xiaomi, Ericsson |
| R2-2501942 |
[Draft] Reply LS on signalling feasibility of dataset and parameter sharing |
Xiaomi, Ericsson |
| R2-2502111 |
Feasibility Analysis on the Alternatives for Two-sided Model |
MediaTek Inc. |
| R2-2502128 |
Further discussion on parameters/model transfer in two-sided model |
Apple |
| R2-2502293 |
Discussion on Dataset and Parameter Sharing from the Network to the UE for Two-Sided Model Training |
Qualcomm Incorporated |
| R2-2502412 |
On Model parameter and Data Set Sharing For Two-side Model |
ZTE Corporation |
| R2-2502732 |
Discussion on AIML model transfer delivery |
CMCC,China Telecom,CATT,ZTE,Apple,Samsung |
| R2-2502797 |
Discussion on signalling feasibility of dataset and parameter sharing for CSI compression |
Huawei, HiSilicon |
| R2-2502926 |
Discussion on model transfer/delivery |
NTT DOCOMO, INC. |
| R2-2502953 |
On signalling feasibility of dataset and parameter sharing |
Ericsson |
| R2-2502959 |
Outstanding issues on signalling feasibility of dataset and parameter sharing for CSI compression |
Samsung R&D Institute UK |
| R2-2503165 |
Reply LS on signalling feasibility of dataset and parameter sharing |
RAN2 |
| R2-2503169 |
Reply LS on signalling feasibility of dataset and parameter sharing |
RAN2 |
| 8.2.1 |
Organizational |
|
| R2-2502258 |
Skeleton of A-IoT MAC specification (TS 38.391) |
Huawei, HiSilicon |
| R2-2502259 |
Initial Text Proposal for A-IoT MAC specification |
Huawei, HiSilicon |
| R2-2502262 |
Illustrative figures for a deeper understanding of A-IoT MAC operations |
Huawei, HiSilicon, China Southern Power Grid |
| R2-2502704 |
Introduction of Ambient IoT |
CMCC |
| 8.2.2 |
A-IoT Paging |
|
| R2-2501788 |
Discussion on ambient IoT paging |
LG Electronics Inc. |
| R2-2501812 |
Discussion on AIoT Paging |
vivo |
| R2-2501828 |
Discussion on A-IoT paging |
HONOR |
| R2-2501846 |
Discussion on Paging for Ambient IoT |
CATT |
| R2-2501962 |
Discussion on A-IOT paging procedure |
Xiaomi |
| R2-2502022 |
Discussion on A-IoT paging message format |
Tejas Network Limited |
| R2-2502028 |
Discussions on AIoT paging |
Fujitsu |
| R2-2502040 |
Discussion on paging procedure for Ambient IoT |
OPPO |
| R2-2502186 |
Discussion on Ambient IoT Paging |
Apple |
| R2-2502206 |
Open issues for A-IoT paging |
ZTE Corporation, Sanechips |
| R2-2502211 |
Email discussion report: [POST129][035][AIoT] Paging |
Qualcomm Incorporated |
| R2-2502215 |
Further discussions on A-IoT paging |
Futurewei |
| R2-2502220 |
Discussion on A-IoT Paging |
ETRI |
| R2-2502268 |
A-IoT paging |
Huawei, HiSilicon |
| R2-2502286 |
Ambient-IoT Paging |
NEC |
| R2-2502345 |
Discussion on paging procedure for Ambient IoT |
Lenovo |
| R2-2502375 |
Discussion on A-IoT paging |
Panasonic |
| R2-2502422 |
Discussion on Paging for A-IoT |
Transsion Holdings |
| R2-2502429 |
Discussion on paging procedure of A-IoT |
Spreadtrum, UNISOC |
| R2-2502484 |
Considerations on paging for Ambient IoT |
Sony |
| R2-2502499 |
Multiple Paging involving reader(s) and service(s) |
Sony |
| R2-2502554 |
Paging Aspects for Ambient IOT |
InterDigital |
| R2-2502607 |
Ambient IoT Paging |
Qualcomm Incorporated |
| R2-2502705 |
Discussion on A-IoT paging |
CMCC |
| R2-2502745 |
Further consideration of A-IoT paging for Ambient IoT |
Kyocera |
| R2-2502753 |
Discussion on A-IoT paging |
ITL |
| R2-2502759 |
Discussion on Ambient IoT Paging |
China Telecom |
| R2-2502765 |
Discussion on DL messages for Ambient IoT UEs |
Ericsson |
| R2-2502775 |
Discussions on AIoT paging |
Samsung |
| R2-2502819 |
Discussion on Ambient IoT paging message design |
ASUSTeK |
| R2-2502873 |
Paging aspects of AIoT |
Nokia |
| R2-2502874 |
Discussion on Ambient IoT Paging |
CEWiT |
| R2-2502938 |
AIoT Paging: Handling a New Service Request |
Philips International B.V. |
| R2-2502954 |
Discussion on paging procedure for Ambient-IoT |
III |
| R2-2502958 |
Discussion on AIoT paging |
NTT DOCOMO, INC. |
| R2-2502989 |
Discussion on DL messages for Ambient IoT UEs |
Ericsson |
| R2-2503155 |
Offline discussion report: [AT129bis][010][AIoT] Paging |
Qualcomm Incorporated |
| 8.2.3 |
A-IoT Random Access |
|
| R2-2501813 |
Random Access Procedure for AIoT Device |
vivo |
| R2-2501829 |
Discussion on A-IoT random access |
HONOR |
| R2-2501847 |
Discussion on random access for A-IoT |
CATT |
| R2-2501859 |
Random Access for Ambient IoT device |
NEC |
| R2-2501963 |
Discussion on access procedure for A-IOT |
Xiaomi |
| R2-2501980 |
A-IoT: ACK/NACK for Msg3 and re-access |
MediaTek Inc. |
| R2-2501987 |
Ambient-IoT Random Access |
Ofinno, LLC |
| R2-2502023 |
Discussion on A-IoT message format for CBRA and CFRA |
Tejas Network Limited |
| R2-2502029 |
Discussions on AIoT Random Access |
Fujitsu |
| R2-2502043 |
Discussion on random access for A-IoT |
OPPO |
| R2-2502151 |
Aspects on RA for AIoT |
Nokia |
| R2-2502187 |
Discussion on Random Access for Ambient IoT |
Apple |
| R2-2502207 |
Open issues for A-IoT random access |
ZTE Corporation, Sanechips |
| R2-2502216 |
Further discussions on A-IoT random access |
Futurewei |
| R2-2502221 |
Considerations for re-access in Ambient IoT |
ETRI |
| R2-2502243 |
Random access procedure for ambient IoT |
China Telecom |
| R2-2502346 |
Discussion on random access for Ambient IoT |
Lenovo |
| R2-2502430 |
Discussion on A-IoT random access |
Spreadtrum, UNISOC |
| R2-2502466 |
Discussion on UL multiple access |
Ericsson |
| R2-2502470 |
A-IoT random access procedure |
Huawei, HiSilicon |
| R2-2502555 |
Random Access Procedure for Ambient IOT |
InterDigital |
| R2-2502578 |
Discussion on re-access mechanism for D2R failures |
Panasonic |
| R2-2502585 |
Views on Random Access Aspects of Ambient IoT |
Qualcomm Incorporated |
| R2-2502623 |
Discussion on re-access for A-IoT |
Continental Automotive |
| R2-2502625 |
Random access types supported by AIoT devices |
NTT DOCOMO, INC. |
| R2-2502691 |
Discussion on random access procedures |
Fraunhofer HHI, Fraunhofer IIS |
| R2-2502717 |
Further consideration on A-IoT random access |
CMCC |
| R2-2502746 |
Further consideration of A-IoT random access for Ambient IoT |
Kyocera |
| R2-2502749 |
Discussion on random access aspects for Ambient IoT |
LG Electronics Inc. |
| R2-2502820 |
Discussion on Ambient IoT Msg2 design |
ASUSTeK |
| R2-2502875 |
Discussion on random access for Ambient IoT |
CEWiT |
| R2-2502905 |
Discussion on random access aspects of Ambient IoT |
KT Corp. |
| R2-2502964 |
Discussion on A-IoT random access |
Samsung Electronics Czech |
| 8.2.4 |
A-IoT Data Transmission and Other general aspects |
|
| R2-2501814 |
AIoT Data Transmission |
vivo |
| R2-2501830 |
Discussion on Data Transmission for Ambient IoT |
HONOR |
| R2-2501848 |
Discussion on data transmission for A-IoT |
CATT |
| R2-2501890 |
Ambient-IoT Data transmission |
NEC |
| R2-2501964 |
Protocol design principle and considerations on Data transmission |
Xiaomi |
| R2-2501965 |
[POST129][036][AIoT] AS ID (Xiaomi) |
Xiaomi |
| R2-2501981 |
Ambient IoT MAC PDU formats |
MediaTek Inc. |
| R2-2502030 |
Discussions on Data Transmission and Other General Aspects |
Fujitsu |
| R2-2502042 |
Discussion on AIoT data transmission related functionalities |
OPPO |
| R2-2502152 |
AIoT data transmission aspects |
Nokia Denmark |
| R2-2502175 |
A-IoT MAC design for data transmission |
Apple |
| R2-2502201 |
Discussion on A-IoT data transmission and other general aspects |
Lenovo |
| R2-2502208 |
Open issues for data transmission and MAC PDU design |
ZTE Corporation, Sanechips |
| R2-2502217 |
Further discussions on A-IoT data transmission and other aspects |
Futurewei |
| R2-2502244 |
A-IoT data transmission and other general aspects |
China Telecom |
| R2-2502269 |
A-IoT data transmission |
Huawei, HiSilicon |
| R2-2502303 |
Data Transmission Aspects for A-IoT |
Ericsson |
| R2-2502343 |
Discussion on AS ID |
Panasonic |
| R2-2502431 |
Discussion on A-IoT data transmission |
Spreadtrum, UNISOC |
| R2-2502485 |
Considerations on segmentation |
Sony |
| R2-2502556 |
Remaining Aspects on AS ID and Segmentation |
InterDigital |
| R2-2502586 |
Data Transmission and Other General Aspects of Ambient IoT |
Qualcomm Incorporated |
| R2-2502671 |
Discussion on A-IoT data transmission |
LG Electronics Inc. |
| R2-2502686 |
Discussion on AIoT data transfer |
NTT DOCOMO, INC. |
| R2-2502696 |
Discussion on data transmission for A-IoT |
CMCC |
| R2-2502747 |
Further consideration of A-IoT data transmission for Ambient IoT |
Kyocera |
| R2-2502776 |
Discussion on A-IoT data transmission |
Samsung |
| R2-2502821 |
Discussion on the assistance information from device |
ASUSTeK |
| R2-2502960 |
Discussion on A-IoT data segmentation and transmission |
III |
| 8.3.1 |
Organizational |
|
| R2-2501821 |
Summary of [POST129][021][AI Mob] TR update (OPPO) |
OPPO. |
| R2-2501822 |
Text proposal of TR 38.744 |
OPPO |
| R2-2502107 |
Discussion on the simulation results illustration for AI mobility |
MediaTek Inc. |
| 8.3.2.1 |
Simulation results |
|
| R2-2502178 |
SLS evaluation results for RRM measurement prediction |
Apple |
| 8.3.2.2 |
Model Generalization |
|
| R2-2501790 |
Simulation results of model generalization on cell configuration |
vivo |
| R2-2501824 |
Discussion on model generalization of RRM measurement prediction |
OPPO |
| R2-2501926 |
Simulation results of Model Generalization |
CATT, Turkcell |
| R2-2501935 |
Discussion on generalization performance over cell configuration |
Xiaomi |
| R2-2502001 |
Discussion on Generalization Issues for AI/ML Mobility |
Samsung |
| R2-2502112 |
Generalization performance evaluation |
MediaTek Inc. |
| R2-2502176 |
On generalization across cell configurations |
Apple |
| R2-2502253 |
Generalization of AIML models for RRM measurement prediction |
Interdigital Inc. |
| R2-2502281 |
Simulation Results for Model Generalization |
Qualcomm Incorporated |
| R2-2502463 |
RRM measurement prediction model generalization evaluation for different cell configurations |
Huawei, HiSilicon |
| R2-2502627 |
Generalization of the AI/ML models for RRM prediction |
Ericsson |
| R2-2502879 |
Evaluation results for RRM measurement prediction generalization |
Nokia |
| R2-2502969 |
Discussion on model generalization of RRM measurement prediction |
ZTE Corporation |
| 8.3.3 |
Measurement event predictions |
|
| R2-2501791 |
Simulation results for measurement event prediction and SLS |
vivo |
| R2-2501823 |
Simulation results of measurement event prediction |
OPPO |
| R2-2501863 |
Simulation assumptions, metrics and specification impact for measurement event prediction |
NEC |
| R2-2501905 |
Discussion on measurement event prediction using large language model |
BJTU |
| R2-2501927 |
Simulation results of measurement event prediction and handover performance |
CATT, Turkcell |
| R2-2501936 |
Discussion on event prediction simulation results |
Xiaomi |
| R2-2502106 |
Discussion and preliminary results for direct and indirect event prediction |
MediaTek Inc. |
| R2-2502138 |
Simulation results for measurement event prediction and system level performance |
Samsung |
| R2-2502230 |
Evaluations on measurement event prediction |
NTT DOCOMO, INC. |
| R2-2502254 |
Measurement event predictions |
Interdigital Inc. |
| R2-2502282 |
Simulation Results for Measurement Event Prediction |
Qualcomm Incorporated |
| R2-2502464 |
Further simulation results for measurement event prediction in FR2 |
Huawei, HiSilicon |
| R2-2502628 |
SLS Results for Event Predictions |
Ericsson |
| R2-2502880 |
On the measurement event prediction |
Nokia |
| R2-2502968 |
Discussion on measurement event prediction |
ZTE Corporation |
| 8.3.4 |
RLF/HO failure prediction |
|
| R2-2502881 |
Considerations on LCM for AIML Mobility |
Nokia |
| 8.3.5 |
LCM and spec impact for AI/ML mobility |
|
| R2-2501789 |
Way forward on study of beam-level prediciton |
vivo, Ericsson, ZTE, Huawei, HiSilicon, CATT, NTT DOCOMO, CMCC, Samsung, Interdigital |
| R2-2501792 |
Discussion on LCM and spec impact |
vivo |
| R2-2501825 |
Discussion on spec impact of AI mobility |
OPPO |
| R2-2501862 |
RRM measurement prediction specification impact discussion |
NEC |
| R2-2501928 |
Specification impact for AIML mobility |
CATT, Turkcell |
| R2-2501937 |
Discussion on LCM and spec impact for AI/ML mobility |
Xiaomi |
| R2-2501990 |
LCM and Spec Impact for AI/ML Mobility |
Lenovo |
| R2-2502003 |
Discussion on AIML mobility LCM procedure |
NEC |
| R2-2502113 |
Discussion on LCM and Specificaton Impact for AI Mobility |
MediaTek Inc. |
| R2-2502139 |
Discussion on LCM and spec impact for AI/ML mobility |
Samsung |
| R2-2502177 |
On LCM for AI/ML mobility |
Apple |
| R2-2502179 |
On standards impacts other than LCM |
Apple |
| R2-2502231 |
Discussions on LCM and specification impact for AI/ML mobility |
NTT DOCOMO, INC. |
| R2-2502255 |
LCM and spec impact for AI/ML mobility |
Interdigital Inc. |
| R2-2502283 |
LCM and specifications impact for AI/ML for mobility |
Qualcomm Incorporated |
| R2-2502437 |
Discussion on LCM and spec impact for AIML mobility |
Spreadtrum, UNISOC |
| R2-2502460 |
Discussion on Specification-related Aspects for AI/ML-based Mobility |
Sharp |
| R2-2502462 |
Discussion on specification impacts of AIML aided mobility |
Huawei, HiSilicon |
| R2-2502500 |
Data collection for event prediction |
Sony |
| R2-2502650 |
Discussion on LCM for AI for Mobility |
Ericsson |
| R2-2502711 |
Discussion on LCM for RRM measurement prediction with UE sided model |
CMCC |
| R2-2502712 |
Discussion on LCM for RRM measurement prediction with NW sided model |
CMCC |
| R2-2502733 |
Discussion on LCM for measurement event prediction |
CMCC |
| R2-2502822 |
Discussion on LCM for AIML Mobility |
ASUSTeK |
| R2-2502925 |
Discussion on LCM and spec impact |
ETRI |
| R2-2502949 |
Discussion on specification impact for event prediction |
KDDI Corporation |
| R2-2502970 |
Discussion on spec impact for AI mob |
ZTE Corporation |
| 8.4.1 |
Organizational |
|
| R2-2501743 |
LS on LP-WUS UE RF (R4-2503003; contact: vivo) |
RAN4 |
| R2-2501954 |
Running 37.340 CR for LP-WUS |
ZTE Corporation, Sanechips |
| R2-2502098 |
Discussion on UE capability for LP-WUS |
Huawei, HiSilicon |
| R2-2502141 |
38.304 Running CR for LP-WUS (CATT) |
CATT |
| R2-2502153 |
RRC Running CR for LP-WUS WUR |
vivo (Rapporteur) |
| R2-2502307 |
Running MAC CR for LP-WUS |
Apple |
| R2-2502913 |
Introduction of Low-Power Wake-Up Signal and Receiver for NR |
Ericsson |
| R2-2503031 |
[AT129bis][201][LPWUS] Proposals for UE ID based sub-grouping (CATT) |
CATT |
| 8.4.2 |
Procedure and configuration of LP-WUS in RRC_IDLE/INACTIVE |
|
| R2-2501831 |
LP-WUS in RRC_IDLE/INACTIVE |
HONOR |
| R2-2501893 |
Discussion on LP-WUS in RRC_IDLE INACTIVE |
NEC |
| R2-2501960 |
Procedure and configuration of LP-WUS for IDLE and INACTIVE mode |
ZTE Corporation, Sanechips |
| R2-2501997 |
Procedure and Configuration of LP-WUS in RRC Idle Inactive Mode |
Samsung |
| R2-2502005 |
Remaining issues on LP-WUS paging monitoring |
Xiaomi Communications |
| R2-2502014 |
IDLE/INACTIVE mode procedures for supporting LP-WUS |
Tejas Network Limited |
| R2-2502097 |
Discussion on procedure and configuration of LP-WUS in RRC_IDLE/INACTIVE |
Huawei, HiSilicon |
| R2-2502143 |
LP-WUS in RRC_IDLE/INACTIVE |
CATT |
| R2-2502155 |
Discussion on LP-WUS WUR in RRC_IDLE INACTIVE |
vivo |
| R2-2502212 |
LP-WUS in IDLE and INACTIVE |
Nokia |
| R2-2502227 |
Remaining issues on LP-WUS in RRC IDLE or INACTIVE |
LG Electronics Inc. |
| R2-2502308 |
Procedure and configuration of LP-WUS in RRC_IDLE/INACTIVE |
Apple |
| R2-2502324 |
Discussion on LP-WUS procedure and configuration |
OPPO |
| R2-2502447 |
LP-WUS operation in IDLE/Inactive state |
Qualcomm Incorporated |
| R2-2502486 |
RAN2 aspects on LP-WUS/WUR in RRC Idle/Inactive mode |
Sony |
| R2-2502597 |
Procedure and Configuration of LP-WUS in RRC IDLE/INACTIVE |
Lenovo |
| R2-2502659 |
Discussion on LP-WUS operation in RRC_IDLE/INACTIVE modes |
InterDigital, Inc. |
| R2-2502743 |
Discussion on LP-WUS in RRC_IDLE and RRC_INACTIVE |
Sharp |
| R2-2502901 |
Further Consideration on LP-WUS operation in IDLE/INACTIVE |
CMCC |
| R2-2502910 |
LP-WUS in idle and inactive |
Ericsson |
| R2-2502976 |
Discussion on the LP-WUS handling for Emergency call back |
NTT DOCOMO INC.. |
| R2-2502977 |
Discussion on the LP-WUS capability issue within non-homogeneous deployment |
NTT DOCOMO INC.. |
| R2-2503182 |
LS on LP-WUS subgrouping progress |
RAN2 |
| 8.4.3 |
RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE |
|
| R2-2501894 |
Discussion on LP-WUS RRM |
NEC |
| R2-2501967 |
Further discussion on the criteria for RRM measurement relaxation and offloading |
Huawei, HiSilicon |
| R2-2501998 |
RRM measurement relaxation and offloading in RRC Idle Inactive Mode |
Samsung |
| R2-2502006 |
Discussion on RRM measurement relaxation for RRC_IDLE_INACTIVE |
Xiaomi Communications |
| R2-2502142 |
Summary of [Post129][212][LPWUS] Running CR for TS 38.304 (CATT) |
CATT |
| R2-2502144 |
RRM Relaxation and Offloading in RRC_IDLE/INACTIVE |
CATT |
| R2-2502154 |
Whether/How to reduce the number of thresholds for LP-WUS monitoring and RRM relaxation/offloading |
vivo |
| R2-2502156 |
Discussion on RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE |
vivo |
| R2-2502213 |
RRM measurement relaxation in RRC_IDLE/INACTIVE |
Nokia |
| R2-2502228 |
Remaining issues on measurement offloading and relaxation |
LG Electronics Inc. |
| R2-2502309 |
RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE |
Apple |
| R2-2502325 |
Discussion on RRM measurement in RRC IDLE and INACTIVE |
OPPO |
| R2-2502351 |
RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE |
Lenovo |
| R2-2502449 |
LP-WUS RRM measurement relaxation and offloading |
Qualcomm Incorporated |
| R2-2502660 |
Discussion on RRM measurement relaxation and offloading |
InterDigital, Inc. |
| R2-2502722 |
Discussion on RRM measurement relaxation and offloading in RRC_IDLE INACTIVE |
CMCC |
| R2-2502744 |
Discussion on RRM measurement relaxation and offloading |
Sharp |
| R2-2502757 |
Discussion on neighboring cell measurement with LR |
InterDigital, Ericsson, Nokia, Sony, Vodafone, KT |
| R2-2502760 |
Discussion on RRM measurement relaxation and offloading for RRC_IDLE and INACTIVE |
China Telecom |
| R2-2502911 |
LP-WUS and RRM measurements |
Ericsson |
| R2-2502931 |
RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE |
ZTE Corporation, Sanechips |
| R2-2502995 |
LP-WUS RRM measurement relaxation and offloading |
Qualcomm Incorporated |
| R2-2503032 |
Discussion report on [AT129bis][202][LPWUS] |
vivo |
| 8.4.4 |
Procedures for LP-WUS in RRC_CONNECTED |
|
| R2-2501769 |
Discussing on LP-WUS monitoring in Connected mode |
Xiaomi |
| R2-2501832 |
Procedures for LP-WUS in RRC_CONNECTED |
HONOR |
| R2-2501895 |
Discussion on LP-WUS in RRC_CONNECTED |
NEC |
| R2-2501955 |
Summary of [Post129][213] LP-WUS in MR-DC |
ZTE Corporation, Sanechips |
| R2-2501961 |
Procedures for LP-WUS in RRC_CONNECTED |
ZTE Corporation, Sanechips |
| R2-2501992 |
Remainng issues on LP-WUS in RRC_CONNECTED |
LG Electronics Inc. |
| R2-2501999 |
Procedures for LP-WUS in RRC Connected Mode |
Samsung |
| R2-2502016 |
LP-WUS operation in Connected mode |
Tejas Network Limited |
| R2-2502145 |
Analysis on LP-WUS for RRC_CONNECTED |
CATT |
| R2-2502157 |
Discussion on LP-WUS WUR in RRC_Connected |
vivo |
| R2-2502310 |
Procedures for LP-WUS in RRC_CONNECTED |
Apple |
| R2-2502326 |
Discussion on LP-WUS in RRC_CONNECTED |
OPPO |
| R2-2502448 |
LP-WUS operation in CONNECTED state |
Qualcomm Incorporated |
| R2-2502471 |
Further discussion on LP-WUS for RRC_CONNECTED mode |
Huawei, HiSilicon |
| R2-2502477 |
LP-WUS in CONNECTED mode |
InterDigital |
| R2-2502598 |
LP-WUS in RRC Connected Mode |
Lenovo |
| R2-2502723 |
Discussion on LP-WUS operation in CONNECTED mode |
CMCC |
| R2-2502882 |
LP-WUS in RRC_CONNECTED |
Nokia, Nokia Shanghai Bell |
| R2-2502912 |
LP-WUS in connected |
Ericsson |
| 8.5.1 |
Organizational |
|
| R2-2501722 |
LS on time location of on-demand SSB for Scell (R1-2501633; contact: LGE) |
RAN1 |
| R2-2501956 |
Running 38.306 CR for NES UE capability |
ZTE Corporation, Sanechips |
| R2-2501984 |
Introduction of Network Energy Savings Enhancements running CR |
Huawei, HiSilicon |
| R2-2502129 |
Summary report of [POST129][104][NES] 38.304 running CR and stage 3 open issues |
Apple (Rapporteur) |
| R2-2502150 |
Summary of Comments to 38.331 CR for NES |
Ericsson |
| R2-2502173 |
Running RRC CR for enhancements for network energy efficiency |
Ericsson |
| R2-2502323 |
Running 38.304 CR for network energy saving |
Apple (Rapporteur) |
| R2-2502584 |
Summary of Comments to 38.321 CR for NES |
InterDigital |
| R2-2502587 |
Running 38.321 CR for network energy saving |
InterDigital |
| R2-2503004 |
[AT129bis ][105] [NES] FFSs to 38.331 CR for NES (Ericsson) |
Ericsson |
| R2-2503005 |
Summary of [AT129b][106][NES] (Apple) |
Apple |
| R2-2503006 |
[AT129bis][107][NES] Open issues for 38.321 CR (InterDigital) |
InterDigital (Rapporteur) |
| R2-2503161 |
LS on DCI-based PRACH adaptation (R1-2503086; contact: Ericsson) |
RAN1 |
| 8.5.2 |
On-demand SSB SCell operation |
|
| R2-2501805 |
Discussion on on-demand SSB |
Xiaomi |
| R2-2501833 |
Discussion on on-demand SSB |
HONOR |
| R2-2501867 |
On-demand SSB SCell Operation |
Samsung |
| R2-2501886 |
Discussion on On-Demand SSB |
OPPO |
| R2-2501901 |
Consideration on on-demand SSB SCell operation |
CATT |
| R2-2501957 |
Remaining issues of on demand SSB Scell operation |
ZTE Corporation, Sanechips |
| R2-2502002 |
Discussion on on-demand SSB SCell operation |
Sharp |
| R2-2502130 |
Remaining issues on on-demand SSB for Scell |
Apple |
| R2-2502136 |
Discussion on OD-SSB |
Rakuten Mobile, Inc |
| R2-2502148 |
Discussion on on-demand SSB for NES |
Ericsson |
| R2-2502219 |
NES SCell handling for OD-SSB |
ETRI |
| R2-2502225 |
Remaining issues on on-demand SSB SCell operation |
Fujitsu |
| R2-2502320 |
Further discussion on On-demand SSB for SCell |
NEC |
| R2-2502371 |
Issues on the procedure of on-demand SSB SCell operation |
Lenovo |
| R2-2502384 |
Remaining issues of on-demand SSB SCell operation |
vivo |
| R2-2502487 |
On-demand SSB Scell operation discussion |
Sony |
| R2-2502540 |
Discussion on On-demand SSB SCell Operation |
Qualcomm Incorporated |
| R2-2502582 |
On demand SSB transmission for SCell |
InterDigital |
| R2-2502724 |
Discussion on On-demand SSB for Scell |
CMCC |
| R2-2502742 |
On-demand SSB SCell operation |
Panasonic |
| R2-2502780 |
Discussion on on-demand SSB SCell operation |
NTT DOCOMO, INC. |
| R2-2502840 |
Discussion on on-demand SSB SCell operation for NES |
Huawei, HiSilicon |
| R2-2502847 |
Discussion on on-demand SSB transmission |
LG Electronics France |
| R2-2502864 |
Discussion on On-demand SSB |
KDDI Corporation (TTC) |
| R2-2502907 |
Discussion on on-demand SSB SCell operation |
Sharp |
| R2-2502915 |
On demand SSB handling |
Nokia, Nokia Shanghai Bell |
| R2-2503015 |
[DRAFT] LS on on-demand SSB |
Apple |
| R2-2503019 |
LS on on-demand SSB |
RAN2 |
| 8.5.3 |
On-demand SIB1 |
|
| R2-2501795 |
Discussion on on-demand SIB1 |
Xiaomi |
| R2-2501834 |
Discussion on on-demand SIB1 |
HONOR |
| R2-2501864 |
Remaining issues for On-demand SIB1 request and UE behaviour |
NEC |
| R2-2501866 |
On-demand SIB1 |
Samsung |
| R2-2501902 |
Consideration on on-demand SIB1 |
CATT |
| R2-2501958 |
Remaining issues of on demand SIB1 |
ZTE Corporation, Sanechips |
| R2-2501982 |
Discussion on remaining issues of on-demand SIB1 operation for NES |
Huawei, HiSilicon |
| R2-2502104 |
Remaining issues on the support for OD-SIB1 |
Google |
| R2-2502131 |
Remaining issues on on-demand SIB1 |
Apple |
| R2-2502134 |
Discussion on on-demand SIB1 for NES |
Rakuten Mobile, Inc |
| R2-2502149 |
Discussion on on-demand SIB1 for NES |
Ericsson |
| R2-2502226 |
Remaining issues on on-demand SIB1 procedure |
Fujitsu |
| R2-2502229 |
Remaining issues on OD-SIB1 |
LG Electronics Inc. |
| R2-2502261 |
Discussion on Ondemand-SIB1 |
KDDI Corporation (TTC) |
| R2-2502385 |
Discussion on OD-SIB1 for RRC IDLE and INACTIVE UE |
vivo |
| R2-2502400 |
Discussion on on-demand SIB1 for handling RLF |
ITRI |
| R2-2502488 |
Remaining details for on-demand SIB1 |
Sony |
| R2-2502541 |
Discussion on On-demand SIB1 |
Qualcomm Incorporated |
| R2-2502577 |
SIB1 acquisition for Rel-19 NES UE in RRC_CONNECTED state |
Fainity Innovation |
| R2-2502580 |
On-demand SIB1 request and reception |
InterDigital |
| R2-2502596 |
Remaining OD SIB1 issues |
Lenovo |
| R2-2502725 |
Discussion on On-demand SIB1 |
CMCC |
| R2-2502761 |
Consideration on on-demand SIB1 |
OPPO |
| R2-2502781 |
Discussion on on-demand SIB1 |
NTT DOCOMO, INC. |
| R2-2502876 |
Discussion on remaining issues of on-demand SIB1 |
SHARP Corporation |
| R2-2502900 |
Discussion on On-demand SIB1 for NES |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2502916 |
On demand SIB1 handling |
Nokia, Nokia Shanghai Bell |
| 8.5.4 |
Adaptation of common signal/channel transmissions |
|
| R2-2501796 |
Discussion on common signal adaptation |
Xiaomi |
| R2-2501817 |
Discussion on adaptation of common signal channel transmission |
OPPO |
| R2-2501865 |
PRACH, paging and SSB adaptation for NES |
NEC |
| R2-2501868 |
Adaptation of common signal channel transmissions |
Samsung |
| R2-2501903 |
Adaptation of Common signal channel transmissions |
CATT |
| R2-2501959 |
Remaining issues of common signal/channel transmissions |
ZTE Corporation, Sanechips |
| R2-2502031 |
Adaptation of common signal or channel |
Fujitsu |
| R2-2502132 |
Remaining issues on common signal transmission adaptation |
Apple |
| R2-2502372 |
Paging and PRACH adaptation |
Lenovo |
| R2-2502386 |
Discussion on adaptation of common signal transmissions |
vivo |
| R2-2502489 |
RAN2 impacts on SSB and RACH adaptations |
Sony |
| R2-2502542 |
Discussion on Adaptation of Common Signal/Channel Transmissions |
Qualcomm Incorporated |
| R2-2502581 |
Time domain adaptation of common signalling and channels |
InterDigital |
| R2-2502726 |
Discussion on Common signalling adaptation |
CMCC |
| R2-2502766 |
Adaptation of common signal/channel transmissions for NES |
Ericsson |
| R2-2502782 |
Discussion on adaptation of common signal and channel |
NTT DOCOMO, INC. |
| R2-2502841 |
Discussion on adaptation of common signals/channels transmissions |
Huawei, HiSilicon |
| R2-2502917 |
Adaptation of common signals |
Nokia, Nokia Shanghai Bell |
| 8.6.1 |
Organizational |
|
| R2-2501709 |
LS on activation/deactivation of semi-persistent CSI-RS resource for LTM candidate cells (R1- 2501500; contact: Fujitsu) |
RAN1 |
| R2-2501715 |
LS on L1filtering for LTM event triggered reporting (R1-2501577; contact: Fujitsu) |
RAN1 |
| R2-2501756 |
Reply LS on security handling for inter-CU LTM in non-DC cases (S3-251124; contact: CATT) |
SA3 |
| R2-2501900 |
Report of [POST129][111][MOB] (CATT) |
CATT |
| R2-2502095 |
Summary of [POST128][108][MOB] RRC running CR (Huawei) |
Huawei, HiSilicon |
| R2-2502096 |
Draft running CR for event-triggered meas report for RRC |
Huawei, HiSilicon |
| R2-2502158 |
Running MAC CR for Mob Ph4 |
vivo (Rapporteur) |
| R2-2502196 |
Introduction of NR mobility enhancements Phase 4 in TS 38.300 |
Apple |
| R2-2502197 |
Report of [POST129][106][Mob] Stage-2 CR 38.300 (Apple) |
Apple |
| R2-2502198 |
Observations on some topics related to Rel-19 Mobility Enh WI |
Apple |
| R2-2502234 |
Introduction of NR mobility enhancements Phase 4 in TS 37.340 |
China Telecom |
| R2-2502256 |
Draft 306 running CR for UE capability for Mob Ph4 |
CATT |
| R2-2502257 |
Draft 331 running CR for UE capability for Mob Ph4 |
CATT |
| R2-2502534 |
Running RRC CR for inter-CU and conditional LTM |
Ericsson |
| R2-2502535 |
List of FFSs for LTM and CLTM |
Ericsson |
| R2-2503001 |
Summary of offlines [AT129b][102][MOB] and [AT129b][110][MOB] |
Ericsson |
| R2-2503003 |
Discussion report on [AT129bis][104][MOB] MAC open issues (vivo) |
vivo |
| R2-2503154 |
Introduction of NR mobility enhancements Phase 4 in TS 38.300 |
Apple |
| 8.6.2 |
Inter-CU LTM |
|
| R2-2501835 |
Further discussion on inter-CU LTM |
HONOR |
| R2-2501887 |
Discussion on open issues for inter-CU LTM |
OPPO |
| R2-2501897 |
Discussion on Inter-CU LTM |
CATT |
| R2-2501929 |
Security discussion and other remaining issues of inter-CU LTM |
MediaTek Inc. |
| R2-2501977 |
Discussion on inter-CU LTM |
Google |
| R2-2501995 |
Remaining issues of inter-CU LTM |
LG Electronics Inc. |
| R2-2502017 |
Remaining Issues for Inter-CU LTM |
Qualcomm Incorporated |
| R2-2502045 |
On remaining issues for Inter-CU LTM |
Nokia |
| R2-2502066 |
Discussion on inter-CU LTM |
Xiaomi |
| R2-2502120 |
Discussion on Inter-CU LTM |
Rakuten Mobile, Inc |
| R2-2502121 |
Discussion on Inter-CU LTM |
Rakuten Mobile, Inc |
| R2-2502122 |
Discussion on Inter-CU LTM |
Rakuten Mobile, Inc |
| R2-2502135 |
Discussion on Inter-CU LTM security and fast recovery |
InterDigital, Europe, Ltd. |
| R2-2502159 |
Discussion on inter-CU LTM |
vivo |
| R2-2502235 |
Discussion on inter-CU LTM |
China Telecom |
| R2-2502285 |
Discussion on inter-CU LTM |
Fujitsu |
| R2-2502299 |
Discussion on inter-CU LTM |
NEC |
| R2-2502340 |
Discussion on inter-CU LTM |
ZTE Corporation, Sanechips |
| R2-2502359 |
Remaining issues for Inter-CU LTM |
Lenovo |
| R2-2502381 |
Discussion on issues for supporting inter-CU LTM |
Sharp |
| R2-2502423 |
Further discussion remaining issues of inter-CU LTM cell switch |
Transsion Holdings |
| R2-2502444 |
Discussion on security for inter-CU LTM |
Ericsson |
| R2-2502481 |
Discussion on inter-CU LTM |
NTT DOCOMO, INC. |
| R2-2502490 |
LTM Resource consumption for the target cells |
Sony |
| R2-2502509 |
Discussion on remaining issues in Inter-CU LTM |
Apple |
| R2-2502601 |
Discussion on open issues for inter-CU LTM |
Ofinno, LLC |
| R2-2502683 |
Discussion on security handling for inter-CU LTM |
KT Corp. |
| R2-2502727 |
Discussion on Inter-CU LTM |
CMCC |
| R2-2502774 |
Further Considerations to Support Inter-CU LTM |
Samsung |
| R2-2502852 |
Further Considerations to Support Inter-CU LTM |
Samsung |
| R2-2502944 |
Inter-CU LTM |
Huawei, HiSilicon |
| R2-2502965 |
Discussion on inter-CU LTM |
DENSO CORPORATION |
| R2-2503011 |
Report of [POST129][111][MOB] (CATT) |
CATT |
| R2-2503012 |
LS on RAN2 agreements for security key handling in inter-CU LTM |
RAN2 |
| 8.6.3 |
L1 event triggered measurement reporting |
|
| R2-2501836 |
Discussion on measurement event evaluation and report |
HONOR |
| R2-2501879 |
Remaining issues of L1 event triggered measurement reporting |
Xiaomi |
| R2-2501888 |
Open issues for event triggered L1 measurement reporting |
OPPO |
| R2-2501898 |
L1 event triggered measurement reporting |
CATT |
| R2-2501930 |
Remaining issues on event triggered L1 MR |
MediaTek Inc. |
| R2-2502019 |
L1 event-triggered measurement reporting for LTM |
Qualcomm Incorporated |
| R2-2502032 |
Discussions on measurement related enhancements for LTM |
Fujitsu |
| R2-2502094 |
Discussion on event-triggered meas report |
Huawei, HiSilicon |
| R2-2502133 |
Discussion on L1 event triggered measurement reporting |
Rakuten Mobile, Inc |
| R2-2502160 |
Discussion on measurement event evaluation and reporting |
vivo |
| R2-2502236 |
Discussion on L1 event triggered measurement reporting |
China Telecom |
| R2-2502311 |
Discussion on L1 event triggered measurement |
Apple |
| R2-2502321 |
Details of MAC CE for event-triggered L1 measurement report |
NEC |
| R2-2502341 |
Discussion on L1 event triggered measurement reporting |
ZTE Corporation, Sanechips |
| R2-2502360 |
Event based L1 measurement report |
Lenovo |
| R2-2502382 |
Discussion on issues for supporting L1 event triggered measurement reporting |
Sharp |
| R2-2502424 |
Discussion on L1 event triggered measurement reporting |
Transsion Holdings |
| R2-2502433 |
Discussion on L1 event triggered measurement reporting |
Spreadtrum, UNISOC |
| R2-2502445 |
Discussion on event-based L1 measurements |
Ericsson |
| R2-2502552 |
Further Details on L1 Measurement Reporting Enhancements for Rel-19 LTM |
Nokia |
| R2-2502602 |
Discussion on L1 event triggered measurement report |
Ofinno, LLC |
| R2-2502606 |
LTM event-triggered measurement reporting |
Fraunhofer HHI, Fraunhofer IIS |
| R2-2502721 |
Discussion on L1 event triggered measurement reporting |
CMCC |
| R2-2502799 |
Remaining Issues of L1 Event Triggered Measurement Report |
Samsung |
| R2-2502823 |
Discussion on MR MAC CE for LTM |
ASUSTeK |
| R2-2502831 |
Discussion on L1 event triggered measurement reporting for LTM |
KDDI Corporation |
| R2-2502950 |
L1 event triggered measurement report |
LG Electronics Inc. |
| R2-2503002 |
Summary of [AT129b][103][MOB] RRC running CR (Huawei) |
Huawei, HiSilicon |
| 8.6.4 |
Conditional intra-CU LTM |
|
| R2-2501826 |
Discussion on Conditional Intra CU LTM |
Lekha Wireless Solutions |
| R2-2501837 |
Discussion on conditional LTM |
HONOR |
| R2-2501889 |
Discussion on conditional LTM |
OPPO |
| R2-2501899 |
Discussion on Conditional Intra-CU LTM |
CATT |
| R2-2501931 |
Further discussion on Conditional LTM |
MediaTek Inc. |
| R2-2501996 |
Remaining issues of CLTM |
LG Electronics Inc. |
| R2-2502018 |
Conditional intra-CU LTM |
Qualcomm Incorporated |
| R2-2502033 |
Discussion on conditional Intra-CU LTM |
Fujitsu |
| R2-2502067 |
Discussion on conditional LTM |
Xiaomi |
| R2-2502118 |
Conditional LTM. |
Interdigital, Inc. |
| R2-2502119 |
Remaining issues of Conditional LTM |
Rakuten Mobile, Inc |
| R2-2502161 |
Discussion on conditional LTM |
vivo |
| R2-2502237 |
Discussion on conditional intra-CU LTM |
China Telecom |
| R2-2502287 |
Remaining open issues for CLTM |
NEC |
| R2-2502289 |
Discussion on Conditional intra-CU LTM remaining issues |
Baicells Technologies Co. Ltd |
| R2-2502312 |
Discussion on conditional Intra-CU LTM |
Apple |
| R2-2502342 |
Discussion on conditional intra-CU LTM |
ZTE Corporation, Sanechips |
| R2-2502383 |
Discussion on issues for supporting conditional LTM |
Sharp |
| R2-2502396 |
CLTM Scenarios and remaining points |
Lenovo |
| R2-2502399 |
Discussion on coexistence of conditional LTM and LTM |
ITRI |
| R2-2502425 |
Discussion on Early TA handling |
Transsion Holdings |
| R2-2502438 |
Discussion on conditional LTM |
Spreadtrum, UNISOC |
| R2-2502446 |
Discussion on Conditional LTM |
Ericsson |
| R2-2502603 |
Discussion on open issues for conditoinal LTM |
Ofinno, LLC |
| R2-2502728 |
Discussion on Conditional LTM |
CMCC |
| R2-2502748 |
Remaining issues on conditional LTM |
ETRI |
| R2-2502756 |
Discussion on Conditional intra-CU LTM |
ITL |
| R2-2502800 |
Remaining Issues of Conditional Intra-CU LTM |
Samsung |
| R2-2502824 |
Discussion on early TAT handling for CLTM |
ASUSTeK |
| R2-2502846 |
Considerations on CLTM TAT handling |
Kyocera |
| R2-2502878 |
On conditional LTM |
Nokia |
| R2-2502945 |
Intra-CU conditional LTM |
Huawei, HiSilicon |
| 8.7.1 |
Organizational |
|
| R2-2501754 |
LS reply on multi-modality awareness (S2-2502465; contact: CMCC) |
SA2 |
| R2-2501757 |
Reply to LS on Application-Layer FEC Awareness at RAN (S4-250252; contact: Qualcomm) |
SA4 |
| R2-2501761 |
Introduction to R19 XR enhancements |
Qualcomm Incorporated |
| R2-2501880 |
UE capabilities for XR |
Xiaomi |
| R2-2501950 |
PDCP running CR for R19 XR |
LG Electronics Inc. (Rapporteur) |
| R2-2501951 |
Discussion of [POST129][511][XR] PDCP running CR |
LG Electronics Inc. (Rapporteur) |
| R2-2502089 |
Draft runnnig RRC CR for R19 XR |
Huawei, HiSilicon |
| R2-2502091 |
Summary for [POST129][510][XR] RRC running CR (Huawei) |
Huawei, HiSilicon |
| R2-2502162 |
RLC Running CR for XR |
vivo |
| R2-2502275 |
Rapporteur Inputs |
Nokia, Qualcomm (Rapporteurs) |
| R2-2502276 |
Draft Stage 2 CR for XR |
Nokia (Rapporteur) |
| 8.7.3 |
RRM measurement gaps/restrictions related enhancements |
|
| R2-2501803 |
Discussion on Measurement Gap enhancements |
OPPO |
| 8.7.4.1 |
LCP enhancements |
|
| R2-2501762 |
Discussion on LCP enhancements |
Qualcomm Incorporated |
| R2-2501815 |
Discussion on LCH priority adjustment for XR |
OPPO |
| R2-2501838 |
Discussion on LCP enhancements |
HONOR |
| R2-2501870 |
Consideration on LCP Enhancement |
CATT |
| R2-2501946 |
Discussion on LCP Enhancements |
Sharp |
| R2-2502008 |
Discussion on LCP enhancements of XR traffic |
Xiaomi Communications |
| R2-2502034 |
Discussions on enhancements for LCH priority-adjusted data |
Fujitsu |
| R2-2502163 |
Remaining issues on LCP enhancements for XR |
vivo |
| R2-2502180 |
Discussions on Delay-based LCP Enhancements |
Apple |
| R2-2502202 |
LCP enhancements for XR |
ZTE Corporation, Sanechips |
| R2-2502265 |
LCP Enhancements for XR |
Nokia, Nokia Shanghai Bell |
| R2-2502295 |
Considerations on LCP enhancements for XR |
NEC |
| R2-2502300 |
Discussion on additional priority based LCP enhancements in XR |
Huawei, HiSilicon |
| R2-2502398 |
Discussion on enhanced LCP for XR |
ITRI |
| R2-2502562 |
Considerations on LCP Enhancements |
China Telecom |
| R2-2502579 |
remaining details on Intra-UE prioritization / LCP enhancements |
Lenovo |
| R2-2502583 |
LCP enhancement for XR |
InterDigital |
| R2-2502718 |
Further consideration on LCP enhancement for XR |
CMCC |
| R2-2502848 |
Remaining issues on LCP enhancement for XR |
LG Electronics Inc. |
| R2-2502934 |
LCP enhancements |
Ericsson |
| R2-2502948 |
Finalising LCP design for XR Ph3 |
Samsung R&D Institute UK |
| 8.7.4.2 |
DSR enhancements |
|
| R2-2501763 |
Discussion on DSR enhancements |
Qualcomm Incorporated |
| R2-2501816 |
Discussion on DSR enhancements for XR |
OPPO |
| R2-2501839 |
Discussion on DSR enhancements |
HONOR |
| R2-2501871 |
Consideration on DSR Enhancement |
CATT |
| R2-2501947 |
Discussion on DSR Enhancements |
Sharp |
| R2-2502007 |
Discussion on DSR enhancements of XR traffic |
Xiaomi Communications |
| R2-2502035 |
Discussions on DSR enhancements |
Fujitsu |
| R2-2502060 |
Remaining issues on DSR enhancements |
TCL |
| R2-2502164 |
Remaining issues on DSR enhancements for XR |
vivo |
| R2-2502181 |
On Data Volume Calculations for Rel-19 DSR |
Apple, CATT, LG Electronics, OPPO, Samsung, Xiaomi |
| R2-2502204 |
DSR enhancements for XR |
ZTE Corporation, Sanechips |
| R2-2502266 |
DSR Enhancements for XR |
Nokia, Nokia Shanghai Bell |
| R2-2502296 |
Considerations on DSR enhancements for XR |
NEC |
| R2-2502301 |
Discussion on DSR enhancements in XR |
Huawei, HiSilicon |
| R2-2502364 |
Enhanced delay status reporting for XR |
Lenovo |
| R2-2502478 |
DSR enhancements for UL scheduling |
InterDigital |
| R2-2502563 |
Remaining Issues on DSR Enhancements |
China Telecom |
| R2-2502719 |
Further consideration on DSR enhancement for XR |
CMCC |
| R2-2502751 |
Remaining Issues on DSR enhancements in Rel-19 XR |
Samsung |
| R2-2502849 |
Discussion on DSR enhancement for XR |
LG Electronics Inc. |
| R2-2502877 |
Discussion on XR DSR enhancements |
III |
| R2-2502932 |
DSR enhancements |
Ericsson |
| 8.7.5 |
RLC enhancements |
|
| R2-2501764 |
Discussion on RLC enhancements |
Qualcomm Incorporated |
| R2-2501802 |
Discussion on RLC re-transmission related enhancements |
OPPO |
| R2-2501840 |
Discussion on RLC enhancements |
HONOR |
| R2-2501872 |
Consideration on XR-specific RLC Enhancement |
CATT |
| R2-2501881 |
RLC AM retransmission enhancements |
Xiaomi |
| R2-2501948 |
Discussion on RLC Enhancements in XR |
Sharp |
| R2-2502036 |
Discussions on RLC enhancements |
Fujitsu |
| R2-2502165 |
Discussion on RLC enhancement for XR |
vivo |
| R2-2502182 |
Discussions on Fast RLC Retransmission |
Apple, Ericsson |
| R2-2502183 |
Views on Avoidance of Unnecessary RLC Retransmissions |
Apple |
| R2-2502203 |
RLC enhancements for XR |
ZTE Corporation, Sanechips |
| R2-2502218 |
On RLC Status report after discarding outdated AMD PDU |
Futurewei |
| R2-2502222 |
Discussion on RLC AM enhancements |
Huawei, HiSilicon |
| R2-2502223 |
Remaining issues on RLC enhancements for XR |
LG Electronics Inc. |
| R2-2502277 |
RLC enhancements |
Nokia, Nokia Shanghai Bell |
| R2-2502302 |
Further discussion on RLC retransmission for XR |
Quectel |
| R2-2502365 |
AM RLC enhancement |
Lenovo |
| R2-2502401 |
Discussion on RLC AM Enhancements |
CANON Research Centre France |
| R2-2502436 |
Discussion on timely RLC retransmission(s) |
Spreadtrum, UNISOC |
| R2-2502479 |
Discussion on RLC enhancements |
InterDigital |
| R2-2502491 |
Timely retransmissions for RLC AM |
Sony, Canon |
| R2-2502501 |
Remainning details on RLC AM enhancement |
NEC |
| R2-2502564 |
Consideration on RLC AM Enhancements |
China Telecom |
| R2-2502673 |
Discussion on UE Capabilities for RLC AM Enhancements |
Ericsson, Qualcomm Incorporated, ZTE Corporation, MediaTek Inc. |
| R2-2502710 |
Discussion on the left issue of RLC enhancements |
CMCC |
| R2-2502853 |
Discussion on RLC enhancements |
DENSO CORPORATION |
| R2-2502860 |
RLC Enhancements for XR |
Samsung |
| R2-2502872 |
Remaining issues on timely RLC retransmission |
TCL |
| R2-2502972 |
Remaining issues for XR RLC AM enhancement |
MediaTek Inc. |
| 8.7.6 |
XR rate control |
|
| R2-2501765 |
Discussion on XR rate control |
Qualcomm Incorporated |
| R2-2501841 |
XR rate control |
HONOR |
| R2-2501873 |
Discussion on XR Rate Control |
CATT |
| R2-2501882 |
XR rate control |
Xiaomi |
| R2-2501949 |
Discussion on Rate Control in XR |
Sharp |
| R2-2502037 |
Discussions on XR rate control |
Fujitsu |
| R2-2502088 |
Discussion on XR rate control |
Huawei, HiSilicon |
| R2-2502166 |
Discussion on XR rate control |
vivo |
| R2-2502205 |
Data rate control for XR applications |
ZTE Corporation, Sanechips |
| R2-2502224 |
Remaining issues on rate control signaling for XR |
LG Electronics Inc. |
| R2-2502298 |
Uplink rate control for XR |
NEC |
| R2-2502461 |
XR Rate Control |
Lenovo |
| R2-2502480 |
Discussion on UL congestion signaling |
InterDigital |
| R2-2502492 |
Recommended bit rate based XR rate control |
Sony |
| R2-2502674 |
Views on XR Rate Control |
Ericsson |
| R2-2502720 |
Further consideration on XR rate control |
CMCC |
| R2-2502750 |
Discussion on UL rate control for Rel-19 XR |
Samsung |
| R2-2502762 |
Discussion on XR rate control |
OPPO |
| R2-2502883 |
XR rate control |
Nokia, Nokia Shanghai Bell |
| R2-2502889 |
Discussion on RAN Awareness and UL Rate Control for XR |
Meta |
| R2-2502890 |
Discussion on XR rate control |
MediaTek Inc. |
| R2-2502957 |
Discussion on Rate Control for XR |
China Telecom |
| 8.8.1 |
Organizational |
|
| R2-2501770 |
Introduction of LTE TN to NR NTN Mobility UE Capability |
vivo |
| R2-2502192 |
Stage 2 Running CR for NR NTN phase 3 |
THALES |
| R2-2502511 |
Discussion on NR NTN UE capabilities |
Apple |
| R2-2502512 |
Draft CR for Rel-19 NR NTN UE capabilities |
Apple |
| R2-2502676 |
Running RRC CR for NR NTN phase 3 |
Ericsson |
| 8.8.2 |
Downlink coverage enhancements |
|
| R2-2501774 |
Discussion on DL Coverage in NTN |
vivo |
| R2-2501798 |
Discussion on DL coverage enhancement |
Xiaomi |
| R2-2501804 |
Discussion on downlink coverage enhancement |
LG Electronics Inc. |
| R2-2501842 |
Discussion on downlink coverage enhancement |
HONOR |
| R2-2501974 |
NTN downlink coverage enhancements |
Nokia, Nokia Shanghai Bell |
| R2-2502038 |
Discussions on downlink coverage enhancement |
Fujitsu |
| R2-2502048 |
Discussion on downlink coverage enhancements in NR NTN |
ETRI |
| R2-2502057 |
Further discussion on downlink coverage enhancements |
CATT |
| R2-2502072 |
Discussion on NR NTN downlink coverage enhancements |
DENSO CORPORATION |
| R2-2502195 |
Discussion on cell barring for NR NTN downlink coverage enhancements |
THALES |
| R2-2502246 |
Further discussion of NR NTN coverage enhancement |
China Telecom |
| R2-2502315 |
Downlink coverage enhancement for NTN |
InterDigital, Europe, Ltd. |
| R2-2502328 |
Discussion on DL coverage enhancement for NTN |
OPPO |
| R2-2502352 |
Further considerations on NR NTN DL-CE |
Lenovo |
| R2-2502377 |
Discussion on Downlink Coverage Enhancements |
Sharp |
| R2-2502397 |
Discussion on supporting location/time-based SMTC selection |
ITRI |
| R2-2502493 |
SMTC impacts due to NTN downlink coverage enhancements |
Sony |
| R2-2502502 |
Downlink coverage enhancement |
NEC |
| R2-2502513 |
DL coverage enhancement in NTN |
Apple |
| R2-2502524 |
Consideration on downlink coverage enhancements |
ZTE Corporation, Sanechips |
| R2-2502629 |
Downlink coverage enhancements and different SMTCs |
TOYOTA Info Technology Center |
| R2-2502652 |
Default extended SSB periodicity |
Qualcomm Incorporated |
| R2-2502667 |
Discussion on Downlink Coverage Enhancement |
Samsung |
| R2-2502678 |
DL coverage enhancements |
Ericsson |
| R2-2502739 |
Analysis on DL coverage enhancements due to extended SSB periodicity |
CMCC |
| R2-2502839 |
Discussion on DL coverage enhancements |
Huawei, HiSilicon, Turkcell |
| R2-2502863 |
Discussion on Downlink Coverage Enhancements |
CSCN |
| R2-2502870 |
Discussion on DL coverage enhancements |
TCL |
| R2-2502947 |
Further discussion on NTN DL coverage enhancements |
NERCDTV |
| R2-2503055 |
Report of [AT129bis][303][R19 NR NTN] SMTC enhancements |
Xiaomi |
| R2-2503056 |
Draft LS on SMTC enhancements |
Xiaomi |
| R2-2503067 |
Draft LS on SMTC enhancements |
Xiaomi |
| R2-2503068 |
LS on SMTC enhancements |
RAN2 |
| 8.8.3 |
Uplink Capacity/Throughput Enhancement |
|
| R2-2502284 |
Discussion on Uplink Capacity/Throughput Enhancement for NTN |
InterDigital, Europe, Ltd. |
| R2-2502329 |
Discussion on Uplink Capacity Enhancement |
OPPO |
| R2-2502525 |
Consideration on uplink capacity enhancements |
ZTE Corporation, Sanechips |
| R2-2502612 |
Discussion on Uplink Capacity Enhancements |
Huawei, HiSilicon, Turkcell |
| R2-2502699 |
Discussion on uplink capacity/throughput enhancement for NR NTN |
CMCC |
| R2-2502856 |
Discussion on UL Capacity and Throughput Enhancement |
Nokia, Nokia Shanghai Bell |
| 8.8.4 |
Support of Broadcast service |
|
| R2-2501775 |
Remaining Issues on MBS Broadcast in NTN |
vivo |
| R2-2501843 |
Discussion on the support of broadcast service |
HONOR |
| R2-2502039 |
Discussions on supporting broadcast service |
Fujitsu |
| R2-2502041 |
Discussion on providing MBS service area in NTN network |
OPPO |
| R2-2502044 |
Discussion on the support of broadcast service in NTN |
ETRI |
| R2-2502058 |
Further discussion on support of broadcast service in NR NTN |
CATT |
| R2-2502064 |
Further Discussion on Support of MBS Broadcast Service |
TCL |
| R2-2502247 |
The signaling design of service area for PWS and MBS |
China Telecom |
| R2-2502353 |
MBS broadcast service continuity in NR NTN |
Lenovo |
| R2-2502354 |
Further considerations on ETWS support in NR NTN |
Lenovo |
| R2-2502376 |
Remaining issues on intended service area |
Sharp |
| R2-2502514 |
Discussion on broadcast service over NTN |
Apple |
| R2-2502526 |
Consideration on broadcast service ehancements |
ZTE Corporation, Sanechips |
| R2-2502537 |
Discussion on the support of broadcast service |
Xiaomi |
| R2-2502551 |
Remaining Aspects of MBS in Rel-19 NR NTN |
Nokia, Nokia Shanghai Bell |
| R2-2502651 |
MBS broadcast service area information |
Qualcomm Incorporated |
| R2-2502668 |
Discussion on Broadcast Service Area |
Samsung |
| R2-2502677 |
Support for broadcast services in NR NTN |
Ericsson |
| R2-2502700 |
Considerations on broadcast service for NR NTN |
CMCC |
| R2-2502741 |
Discussion on support for broadcast service in NTN |
LG Electronics Inc. |
| R2-2502946 |
Discussion on MBS broadcast over NTN |
Huawei, HiSilicon, China Southern Power Grid, Turkcell |
| R2-2503057 |
Report of [AT129bis][304][R19 NR NTN] Service continuity |
Apple |
| 8.8.5 |
Support of regenerative payload |
|
| R2-2502494 |
Satellite switch with re-sync in regenerative payload |
Sony |
| R2-2502630 |
Regenerative payload for NTN for NR Ph3 |
TOYOTA Info Technology Center |
| R2-2502885 |
Regenerative payload |
Ericsson |
| 8.8.6 |
LTE to NR NTN mobility |
|
| R2-2501776 |
Remaining Issues on LTE to NR NTN Mobility |
vivo |
| R2-2502056 |
Discussion on a remaining issue for LTE_TN_NR_NTN_mob WI |
CATT |
| R2-2502690 |
Remaining issues on E-UTRAN to NR NTN mobility |
Samsung |
| 8.9.1 |
Organizational |
|
| R2-2501720 |
Reply LS on PWS support in RRC_CONNECTED for NB-IoT NTN (R1-2501613; contact: InterDigital) |
RAN1 |
| R2-2501753 |
Reply LS on Satellite IDs for store-and-forward operation (S2-2502450; contact: CICT Mobile, CATT) |
SA2 |
| R2-2501969 |
RRC Running CR for IoT NTN |
Huawei, HiSilicon |
| R2-2501979 |
Running CR for TS36.304 for IoT-NTN |
Nokia |
| R2-2502768 |
MAC Running CR for Rel-19 IoT NTN |
MediaTek Inc. |
| R2-2502887 |
Draft Introduction of IoT NTN phase 3 |
Ericsson |
| 8.9.2 |
Support of Store & Forward |
|
| R2-2501766 |
Discussion on Store and Forward operation |
Xiaomi |
| R2-2501777 |
Further Discussion on S&F Operation |
vivo |
| R2-2501818 |
Remaining issues on S&F operation in IoT NTN |
ZTE Corporation, Sanechips |
| R2-2501844 |
Discussion on the Store and Forward satellite operation |
HONOR |
| R2-2502046 |
RAN2 impacts for SF Operation |
Nokia , Nokia Shanghai Bells |
| R2-2502053 |
Discussion on RAN2 impacts for the support of S&F operation |
CATT |
| R2-2502068 |
Discussion on Store & Forward satellite operation |
OPPO |
| R2-2502073 |
Discussion on Store & Forward operation |
DENSO CORPORATION |
| R2-2502101 |
On the support for the S&F operation |
Google |
| R2-2502116 |
Store and Forward Cell Access Restrictions |
Interdigital, Inc. |
| R2-2502245 |
Further consideration of IoT NTN Store & Forward |
China Telecom |
| R2-2502355 |
Mode transition time for S&F operation |
Lenovo |
| R2-2502426 |
Discussion on support of Store&Forward |
Transsion Holdings |
| R2-2502503 |
Radio Interface Aspect of S&F |
NEC |
| R2-2502515 |
Support of S&F operation in IoT NTN |
Apple |
| R2-2502613 |
Further consideration on Store and Forward |
Huawei, HiSilicon, Turkcell |
| R2-2502620 |
Discussion on Paging and Mode Switching |
Toyota ITC |
| R2-2502622 |
CIoT UP solution for Store & Forward satellite operation |
SHARP Corporation |
| R2-2502655 |
Switching of S&F mode |
Qualcomm Incorporated |
| R2-2502679 |
Support for store and forward in IoT NTN |
Ericsson |
| R2-2502685 |
IoT-NTN S&F Mode Change Indication |
PANASONIC |
| R2-2502688 |
Further discussion on Store and Forward |
Samsung |
| R2-2502698 |
Discussion on IoT NTN Store and Forward |
CMCC |
| R2-2502769 |
RAN2 impact on S&F mode |
MediaTek Inc. |
| R2-2502805 |
Discussion on Store and Forward satellite operation |
ETRI |
| R2-2502825 |
Discussion on time information for S&F |
ASUSTeK |
| R2-2502845 |
Discussion on Store and Forward satellite operation |
ETRI, Korea University |
| R2-2502871 |
Discussion on Store & Forward satellite operation |
TCL |
| R2-2503070 |
LS on S&F mode indications to NAS |
CATT |
| 8.9.3 |
Uplink Capacity Enhancement |
|
| R2-2501767 |
Discussion on uplink capacity enhancements for IoT NTN |
Xiaomi |
| R2-2501778 |
Discussion on CB-EDT Mechanism |
vivo |
| R2-2501794 |
Further considerations on Locating of CB-Msg3 Replicas for DSA |
NTPU |
| R2-2501819 |
Further consideration on UL capacity enhancements in IoT NTN |
ZTE Corporation, Sanechips |
| R2-2501845 |
Discussion on UL capacity enhancement |
HONOR |
| R2-2501966 |
Further consideration on UL capacity enhancement |
Huawei, HiSilicon, Turkcell |
| R2-2502054 |
Further consideration on UL capacity enhancements |
CATT |
| R2-2502069 |
Discussion on CB-msg3 EDT and msg4 enhancement |
OPPO |
| R2-2502099 |
Further consideration on UL capacity enhancement for IoT NTN |
Nokia, Nokia Shanghai Bell |
| R2-2502117 |
CB-EDT |
Interdigital, Inc. |
| R2-2502356 |
EDT for uplink capacity enhancement in NTN |
Lenovo |
| R2-2502402 |
Discussion on UL Capacity Enhancement for IoT-NTN |
NEC |
| R2-2502427 |
Discussion on Uplink Capacity enhancement |
Transsion Holdings |
| R2-2502428 |
Remaining issues on CB-Msg3 transmission |
Spreadtrum, UNISOC |
| R2-2502457 |
On procedures for contention-based Msg3 |
Samsung |
| R2-2502516 |
Uplink capacity enhancement in IoT NTN |
Apple |
| R2-2502656 |
CB-Msg3 and Msg4 enhancements |
Qualcomm Incorporated |
| R2-2502701 |
Further discussion on uplink capacity enhancement for IoT-NTN |
CMCC |
| R2-2502771 |
Discussion on CB-Msg3 procedure |
MediaTek Inc. |
| R2-2502773 |
Report of [Post129][307][R19 IoT NTN] CB-msg3/CB-msg4 |
MediaTek Inc. |
| R2-2502886 |
UL capacity enhancements for IoT NTN |
Ericsson |
| R2-2503058 |
Report of [AT129bis][30x][R19 IoT NTN] Single vs. Multiple (MediaTek) |
MediaTek |
| R2-2503059 |
Report of [AT129bis][305][R19 IoT NTN] CB-msg3-EDT – phase2 |
MediaTek |
| R2-2503060 |
Draft LS on CB-msg3-EDT shared resource configuration |
MediaTek |
| R2-2503175 |
LS on CB-msg3-EDT |
RAN2 |
| 8.9.4 |
Support of PWS |
|
| R2-2501768 |
PWS support for NB-IoT over NTN |
Xiaomi |
| R2-2501779 |
Further Discussion on PWS Support for NB-IoT |
vivo |
| R2-2501820 |
Remaining issues on PWS support in IoT NTN |
ZTE Corporation, Sanechips |
| R2-2501983 |
Remaining issues on PWS support for NB-IoT |
Huawei, HiSilicon, Novamint, Sateliot, Thales, Inmarsat, Viasat, Turkcell |
| R2-2502055 |
Remaining issue on support of PWS for NB-IoT NTN UE |
CATT |
| R2-2502070 |
Discussion on PWS for NB-IoT |
OPPO |
| R2-2502102 |
Remaining issues on support of PWS for NB-IoT NTN |
Nokia, Nokia Shanghai Bell |
| R2-2502103 |
On the support for PWS in NB-IoT |
Google |
| R2-2502357 |
Further considerations on PWS broadcast support in IoT NTN |
Lenovo |
| R2-2502458 |
Acceptable cell camping for NB-IoT |
Samsung, Iridium, Vivo |
| R2-2502657 |
Discussion on PWS in NB-IoT NTN |
Qualcomm Incorporated |
| R2-2502680 |
Enhancements to support PWS in NB-IoT NTN |
Ericsson |
| R2-2502702 |
Support of PWS messages for NB-IoT |
CMCC |
| R2-2502770 |
Discussion on supporting PWS for NB-IoT |
MediaTek Inc. |
| 8.10.1 |
Organizational |
|
| R2-2501912 |
Views on R19 SONMDT UE capabilities |
CATT |
| R2-2501913 |
Introduction of SONMDT UE Capabilities |
CATT |
| R2-2501914 |
Introduction of SONMDT UE Capabilities |
CATT |
| R2-2501915 |
Introduction of SONMDT UE Capabilities |
CATT |
| R2-2502649 |
Running CR for SONMDT features |
Ericsson |
| R2-2502787 |
Running 36.331 CR for R19 SONMDT |
Huawei, HiSilicon |
| R2-2502788 |
Open issue list for running 36.331 CR for R19 SONMDT |
Huawei, HiSilicon |
| R2-2502974 |
Discussion on Rel-19 SONMDT open issues |
Xiaomi |
| R2-2503101 |
[AT129bis][601][SONMDT] Address open issues for RRC |
Ericsson |
| 8.10.2 |
MRO enhancements for Rel-18 mobility features |
|
| R2-2502927 |
Remaining issues for MRO |
ZTE Corporation, Sanechips |
| 8.10.2.1 |
LTM |
|
| R2-2501916 |
MRO Enhancements for LTM |
CATT |
| R2-2502288 |
MRO enhancement for LTM |
NEC |
| R2-2502347 |
Discussion on MRO enhancements for LTM |
Lenovo |
| R2-2502408 |
MRO for LTM and near failure handling for CHO with candidate SCGs |
Nokia |
| R2-2502450 |
SON and MDT for LTM |
Qualcomm Incorporated |
| R2-2502531 |
Discussion on MRO enhancements |
Samsung |
| R2-2502604 |
Discussion on MRO for LTM |
Ofinno, LLC |
| R2-2502646 |
Further considerations on Mobility Robustness Optimization |
Ericsson |
| R2-2502707 |
MRO enhancements for LTM |
CMCC |
| R2-2502789 |
Discussion on MRO for LTM |
Huawei, HiSilicon |
| R2-2502806 |
MRO for LTM |
LG Electronics Inc. |
| R2-2502826 |
Discussion on random access report for LTM |
ASUSTeK |
| R2-2502858 |
RA information enhancement for LTM |
SHARP Corporation |
| 8.10.2.2 |
CHO with candidate SCGs |
|
| R2-2501917 |
New SHR Trigger for CHO with Candidate SCGs |
CATT, Vivo, Lenovo, Huawei, HiSilicon, CMCC |
| R2-2502348 |
Discussion on MRO enhancements for CHO with candidate SCGs |
Lenovo |
| R2-2502451 |
SON and MDT for CHO with candidate SCGs |
Qualcomm Incorporated |
| R2-2502708 |
MRO enhancements for CHO with candidate SCGs |
CMCC |
| R2-2502790 |
Discussion on MRO for CHO with candidate SCGs |
Huawei, HiSilicon |
| R2-2502807 |
MRO for CHO and Associated CPAC |
LG Electronics Inc. |
| R2-2502861 |
SON enhancement for CHO with candidate SCG |
SHARP Corporation |
| 8.10.3 |
SON/MDT for Slicing |
|
| R2-2501734 |
LS on SON for Network Slicing (R3-250914; contact: ZTE) |
RAN3 |
| R2-2502409 |
Enhancements for network slicing (LS R3-250914) |
Nokia |
| R2-2502452 |
SON and MDT for slicing |
Qualcomm Incorporated |
| R2-2502518 |
Discussion on MDT for Slicing |
Samsung |
| R2-2502647 |
Discussion on slice base cell reselection information in Logged MDT |
Ericsson |
| R2-2502738 |
Discussion on SONMDT for network slicing |
CMCC |
| R2-2502791 |
Discussion on SONMDT for Slicing |
Huawei, HiSilicon |
| R2-2502928 |
SON/MDT for Slicing |
ZTE Corporation, Sanechips |
| 8.10.4 |
SON/MDT for NTN |
|
| R2-2501918 |
Consideration on SONMDT enhancements for intra-NTN mobility |
CATT |
| R2-2502242 |
SON of intra-NTN mobility |
China Telecom |
| R2-2502349 |
Discussion on MRO for intra-NTN mobility |
Lenovo |
| R2-2502439 |
SON/MDT for NTN |
Samsung |
| R2-2502453 |
SON and MDT for NTN |
Qualcomm Incorporated |
| R2-2502641 |
MRO for NTN RACH-less Access |
Nokia |
| R2-2502648 |
Discussion on the reply LS to RAN3 on SON-MDT enhancements for NTN |
Ericsson |
| R2-2502792 |
Discussion on SONMDT for NTN |
Huawei, HiSilicon |
| R2-2502808 |
NTN Logging for Unchanged PCI Mobility |
LG Electronics Inc. |
| R2-2502929 |
SON/MDT for NTN |
ZTE Corporation, Sanechips |
| R2-2502975 |
Discussion on SONMDT for NTN mobility |
Xiaomi |
| R2-2503117 |
Relay LS on MDT for NTN |
RAN2 |
| 8.10.5 |
Leftovers from Rel-18 |
|
| R2-2501919 |
MHI Enhancement for SCG Activation and Deactivation |
CATT |
| R2-2502350 |
Discussion on RACH optimization for SDT |
Lenovo |
| R2-2502410 |
MHI/UHI Enhancement for SCG Deactivation/Activation |
Nokia |
| R2-2502482 |
SON/MDT for Leftovers from Rel-18 |
Samsung |
| R2-2502709 |
MHI/UHI Enhancement for SCG Deactivation/Activation |
CMCC |
| R2-2502859 |
RA report enhancements for SDT |
SHARP Corporation |
| R2-2502862 |
MHI enhancement for SCG activation/deactivation |
SHARP Corporation |
| R2-2502930 |
Remaining issues for Rel-18 leftovers |
ZTE Corporation, Sanechips |
| R2-2502951 |
On remaining issues related to Rel.18 leftovers |
Ericsson |
| 8.11.1 |
Organizational |
|
| R2-2501713 |
Reply LS on CSI-RS measurement with SBFD operation (R1-2501560; contact: MediaTek) |
RAN1 |
| R2-2501731 |
SBFD information exchange among gNBs for CLI mitigation (R3-250888; contact: Huawei) |
RAN3 |
| R2-2501738 |
LS on L1 CLI measurement (R4-2502632; contact: Huawei) |
RAN4 |
| R2-2501851 |
TS 38300 Running CR for SBFD |
CATT |
| R2-2502210 |
Summary of [Post129][217][SBFD] List of open issues of RRC impact |
Huawei, HiSilicon (Rapporteur) |
| R2-2502279 |
TS38.304 impacts on supporting Rel-19 SBFD |
NEC |
| R2-2502549 |
RRC running CR for Evolution of NR duplex operation (SBFD) |
Huawei, HiSilicon |
| R2-2502567 |
Introduction of SBFD UE capabilities (Running CR) |
Ericsson |
| R2-2502568 |
Introduction of SBFD UE capabilities (Running CR) |
Ericsson |
| R2-2502591 |
MAC running CR for Evolution of NR duplex operation: SBFD |
Samsung |
| R2-2502978 |
RRC running CR for Evolution of NR duplex operation (SBFD) |
Huawei, HiSilicon |
| 8.11.2 |
Random access in SBFD |
|
| R2-2501797 |
Discussion on RACH in SBFD |
Xiaomi |
| R2-2501849 |
Random Access in SBFD symbols |
CATT |
| R2-2501860 |
Random Access for SBFD Operation |
NEC |
| R2-2501878 |
Impacts on the random access by the evolution of duplex operation |
Huawei, HiSilicon |
| R2-2501945 |
Discussion on Random Access in SBFD |
Sharp |
| R2-2502000 |
Random access in SBFD |
Samsung |
| R2-2502082 |
Discussion on random access procedure in SBFD |
ZTE Corporation |
| R2-2502316 |
Random Access Operation of SBFD |
Nokia Corporation |
| R2-2502387 |
Discussion on random access procedure in SBFD |
vivo |
| R2-2502394 |
Remaining issues of SBFD RACH procedure |
OPPO |
| R2-2502495 |
Random access for SBFD Operation |
Sony |
| R2-2502510 |
Remaining issues for RACH in SBFD |
Apple |
| R2-2502565 |
SBFD RA aspects |
Ericsson |
| R2-2502566 |
CSI-RS measurements and SBFD operation in CA and DC |
Ericsson |
| R2-2502588 |
Views on random access for SBFD |
Qualcomm Incorporated |
| R2-2502642 |
Discussion on Random Access operation in SBFD |
InterDigital, Inc. |
| R2-2502706 |
Discussion on random access in SBFD |
CMCC |
| R2-2502850 |
Discussion on Random Access procedure for SBFD |
LG Electronics Inc. |
| R2-2502967 |
Random Access in SBFD |
Lenovo |
| 8.11.3 |
Other aspects |
|
| R2-2501850 |
Discussion on other aspects of SBFD |
CATT |
| R2-2501883 |
Other aspects of SBFD |
Xiaomi |
| R2-2502083 |
Discussion on multiple carrier and measurements in SBFD |
ZTE Corporation |
| R2-2502318 |
Other impacts by the evolution of duplex operation |
Huawei, HiSilicon |
| R2-2502388 |
SBFD other aspects |
vivo |
| R2-2502395 |
Discussion on the SBFD related measurement and BFR |
OPPO |
| R2-2502589 |
Other aspects of SBFD |
Qualcomm Incorporated |
| R2-2502644 |
Discussion on resource configuration in SBFD |
InterDigital, Inc. |
| R2-2502801 |
Other Aspects of SBFD |
Samsung |
| R2-2502851 |
Other aspects on SBFD |
LG Electronics Inc. |
| R2-2502918 |
Other aspects of SBFD |
Nokia |
| 8.12.1 |
Organizational |
|
| R2-2501705 |
LS to RAN2 on MAC impacts for Rel-19 NR MIMO Ph5 (R1-2500846; contact: Samsung) |
RAN1 |
| R2-2502545 |
Running CR for MIMO Phase 5 |
Ericsson |
| R2-2502664 |
Introduction of Rel-19 MIMO |
Samsung |
| R2-2502715 |
Work Plan for Rel-19 on NR MIMO Phase 5 |
CMCC,Samsung,MediaTek |
| R2-2502716 |
Draft Running 38300 CR for Rel-19 MIMO Phase 5 |
CMCC,Samsung,MediaTek |
| R2-2502988 |
Draft Running 38300 CR for Rel-19 MIMO Phase 5 |
CMCC |
| 8.12.2 |
Asymmetric DL sTRP/UL mTRP |
|
| R2-2501943 |
Discussion on Asymmetric DL sTRP/UL mTRP |
Xiaomi |
| R2-2501993 |
Consideration on Asymmetric DL sTRP/UL mTRP |
LG Electronics Inc. |
| R2-2502063 |
Further discussion on asymmetric DL sTRP and UL mTRP |
SHARP Corporation |
| R2-2502146 |
Discussion on Asymmetric DL sTRP UL mTRP |
CATT |
| R2-2502167 |
Discussion on MAC CE impact for asymmetric DL sTRP/UL mTRP scenarios |
vivo |
| R2-2502304 |
Asymmetric DL/UL mTRP user plane impacts |
Ericsson |
| R2-2502317 |
RAN2 Aspects of Asymmetric DL sTRP/UL mTRP |
Nokia Corporation |
| R2-2502373 |
Discussion on PL offset |
Lenovo |
| R2-2502392 |
Discussion on the remaining issues of the pathloss offset update |
OPPO |
| R2-2502496 |
Enhancement for Asymmetric DL sTRP/UL mTRP |
Sony |
| R2-2502536 |
Discussion on asymmetric DL sTRP/UL mTRP |
China Telecommunications Corp. |
| R2-2502543 |
Discussion on UL only mTRP |
Qualcomm Incorporated |
| R2-2502665 |
Discussion on Asymmetric DL sTRP/UL mTRP |
Samsung |
| R2-2502713 |
Discussion on Asymmetric DL sTRP/UL mTRP |
CMCC |
| R2-2502827 |
Discussion on PL offset value for Asymmetric DL sTRP/UL mTRP |
ASUSTeK |
| R2-2502834 |
Discussion on remaining issues on Asymmetric DL sTRP/UL mTRP |
Huawei, HiSilicon |
| R2-2502866 |
Consideration on the Remaining Issues of PL Offset MAC CE |
ZTE Corporation |
| R2-2503033 |
Discussion on Asymmetric DL sTRP/UL mTRP |
CMCC |
| 8.12.3 |
Others |
|
| R2-2501944 |
Discussion on open issues of RRC spec impact |
Xiaomi |
| R2-2501986 |
Enhancements for UE-initiated/event-driven beam management |
Ofinno, LLC |
| R2-2501994 |
Discussion on UEI beam reporting impact |
LG Electronics Inc. |
| R2-2502065 |
Further discussion on UE-initiated/event-driven beam management |
SHARP Corporation |
| R2-2502147 |
Discussion on UE-initiated Beam Reporting and CSI Enhancement |
CATT |
| R2-2502168 |
Discussion on UE-initiated/event-driven beam management |
vivo |
| R2-2502267 |
Discussion on UE initiated beam reporting |
China Telecommunications Corp. |
| R2-2502314 |
Discussion on UE-initiated Beam Reporting |
Apple |
| R2-2502319 |
RAN2 Aspects of the NR MIMO |
Nokia Corporation |
| R2-2502374 |
Discussion on UEIBR |
Lenovo |
| R2-2502393 |
Clarification on the uplink grant used for the UE initiated beam report |
OPPO |
| R2-2502544 |
Discussion on UE Initiated Beam Report |
Qualcomm Incorporated |
| R2-2502546 |
Report of [Post129][208][ MIMO_Ph5] |
Ericsson |
| R2-2502547 |
Impacts from other NR MIMO Phase 5 objectives |
Ericsson |
| R2-2502666 |
Discussion on UE-initiated Beam Reporting and CSI enhancement |
Samsung |
| R2-2502714 |
Discussion on UE-initiated/event-driven beam management |
CMCC |
| R2-2502828 |
Discussion on MAC impact regarding UEI reporting |
ASUSTeK |
| R2-2502833 |
Enhancements for UE-initiated/event-driven beam management |
Huawei, HiSilicon |
| R2-2502867 |
Consideration on the UEIBM and Other Issues |
ZTE Corporation |
| R2-2503036 |
Way forward on the uplink grant used for UEIBR |
OPPO, Huawei, Ofinno, Samsung, ZTE, Qualcomm, LG, Nokia, ASUSTeK |
| 8.13.1 |
Organizational |
|
| R2-2501874 |
Introduction of Service Continuity for MH Sidelink Relay in 38331 |
CATT |
| R2-2501938 |
Introduction of multi-hop U2N relay in TS 38.304 |
MediaTek Inc. |
| R2-2502278 |
Terminology for specifications of L2 multi-hop relay |
LG Electronics France |
| R2-2502469 |
Introduction of multi-hop U2N relay in TS 38.323 |
Ericsson |
| R2-2502557 |
Draft Running CR for 38.321 |
InterDigital |
| R2-2502608 |
Introduction of NR sidelink multi-hop relay in TS 38.331 |
Huawei, HiSilicon |
| R2-2502695 |
Multi-hop U2N Relay in TS 38.300 |
LG Electronics Inc. |
| R2-2502980 |
Introduction of NR sidelink multi-hop relay in TS 38.351 |
OPPO |
| R2-2503071 |
Introduction of Service Continuity for MH Sidelink Relay in 38331 |
CATT |
| R2-2503072 |
Introduction of multi-hop U2N relay in TS 38.304 |
MediaTek Inc. |
| R2-2503073 |
Introduction of multi-hop U2N relay in TS 38.323 |
Ericsson |
| R2-2503074 |
Draft Running CR for 38.321 |
InterDigital |
| R2-2503075 |
Introduction of NR sidelink multi-hop relay in TS 38.331 |
Huawei, HiSilicon |
| R2-2503076 |
Multi-hop U2N Relay in TS 38.300 |
LG Electronics Inc. |
| R2-2503077 |
Introduction of NR sidelink multi-hop relay in TS 38.351 |
OPPO |
| R2-2503086 |
[AT129bis][407][Relay] Rel-19 relay CR to 38.300 (LG) |
LG |
| R2-2503088 |
Multi-hop U2N Relay in TS 38.300 |
LG Electronics Inc. |
| 8.13.2 |
Relay discovery and (re)selection |
|
| R2-2501799 |
Discovery and relay (re)selection for multi-hop U2N relay |
OPPO |
| R2-2501854 |
Discussion on Relay discovery and (re)selection |
ZTE Corporation, Sanechips |
| R2-2501875 |
Discussion on Multi-hop Discovery and (Re)selection |
CATT |
| R2-2502010 |
Discussion on multi-hop U2N relay discovery and relay selection |
NEC |
| R2-2502188 |
Relay discovery and selection for Multi-hop UE-to-NW Relay |
Apple |
| R2-2502200 |
Discovery and relay reselection for multihop relay |
Nokia |
| R2-2502241 |
Multi-hop relay discovery and reselection |
China Telecom |
| R2-2502361 |
Relay (re)selection in Multi-hop relay |
Lenovo |
| R2-2502378 |
discussion on Relay discovery and (re)selection for multi-hop relay |
Sharp |
| R2-2502418 |
Discussion on relay UE (re)selection for intermediate relay UE |
vivo |
| R2-2502454 |
Discovery and Relay (re)selection for multi-hop U2N relay |
Qualcomm Incorporated |
| R2-2502468 |
Discussion on relay discovery and relay (re)selection |
Ericsson |
| R2-2502497 |
Multi-hop relay selection/re-selection |
Sony |
| R2-2502558 |
Discovery and Relay (Re)Selection for Multi-hop U2N Relays |
InterDigital |
| R2-2502609 |
Relay discovery and (re)selection for multi-hop Relay |
Huawei, HiSilicon |
| R2-2502624 |
Relay (re)selection under multihop relay |
Kyocera |
| R2-2502693 |
Discussion on the discovery and relay (re)selection for multi-hop U2N relay |
LG Electronics Inc. |
| R2-2502777 |
Considerations on relay discovery and (re)selection |
Samsung |
| R2-2502829 |
One remaining issue on multi-hop U2N Relay Discovery message forwarding for model B |
ASUSTeK |
| R2-2503085 |
FFS issues on (re)selection |
Huawei, HiSilicon |
| 8.13.3 |
Control Plane Procedures and SRAP impact |
|
| R2-2501801 |
Control plane procedures of multi-hop U2N relay |
OPPO |
| R2-2501853 |
Discussion on control plane procedures for multi-hop SL Relay |
ZTE Corporation, Sanechips |
| R2-2501861 |
Control Plane aspects for Multi-hop Relay |
NEC |
| R2-2501876 |
Discussion on the Control Plane Procedures |
CATT |
| R2-2502189 |
Fast & Parallel RRC Establishment/Configuration for Multi-hop U2N relaying |
Apple, FirstNet, Ericsson, AT&T, Kyocera |
| R2-2502190 |
Text Proposal for TS 38.351 for fast SRB0/1 forwarding |
Apple |
| R2-2502191 |
Report of [POST129][402][Relay] Control plane approach 2 impact (Apple/Ericsson) |
Apple, Ericsson |
| R2-2502194 |
Control plane and SRAP for multi-hop relay |
Nokia |
| R2-2502232 |
Discussion on control plane aspects for NR sidelink multi-hop relay |
China Telecom |
| R2-2502362 |
Control plane in Multi-hop relay |
Lenovo |
| R2-2502379 |
discussion on C-plane procedure for multi-hop relay |
Sharp |
| R2-2502419 |
Discussion on SRAP impact for baseline procedure |
vivo |
| R2-2502432 |
Discussion on control plane for NR sidelink multi-hop relay |
Spreadtrum, UNISOC |
| R2-2502455 |
Open issue for control plane |
Qualcomm Incorporated |
| R2-2502467 |
Discussion on control plane procedures |
Ericsson |
| R2-2502559 |
Control Plane Handling for Multi-hop U2N Relays |
InterDigital |
| R2-2502610 |
Control plane procedures for multi-hop relay |
Huawei, HiSilicon |
| R2-2502684 |
Discussion on control plane procedure for SL relay |
KT Corp. |
| R2-2502692 |
Discussion on the control plane procedure for multi-hop U2N relay |
LG Electronics Inc. |
| R2-2502778 |
Consideration on CP issues for multi-hop SL relay |
Samsung |
| R2-2502830 |
Issues on SRAP operations for supporting multi-hop L2 U2N Relay |
ASUSTeK |
| R2-2502939 |
SRAP design for R19 multi-hop SL relaying |
Samsung R&D Institute UK |
| R2-2503078 |
Fast/Parallel RRC Setup for MH relay |
Apple |
| 8.13.4 |
Service continuity |
|
| R2-2501800 |
Service continuity of multi-hop U2N relay |
OPPO |
| R2-2501855 |
Discussion on Service continuity |
ZTE Corporation, Sanechips |
| R2-2501877 |
Intra-gNB Service Continuity for Multi-hop U2N Relay |
CATT |
| R2-2501891 |
Considerations on Service Continuity of Multi-hop Relay |
NEC Corporation (ARIB) |
| R2-2501892 |
Considerations on Service Continuity of Multi-hop Relay |
NEC |
| R2-2502199 |
Service continuity aspects of multi-hop relay |
Nokia |
| R2-2502233 |
Discussion on service continuity for multi-hop relay |
China Telecom |
| R2-2502363 |
Service continuity for Multi-hop system |
Lenovo |
| R2-2502380 |
discussion on service continuity for multi-hop relay |
Sharp |
| R2-2502420 |
Discussion on service continuity for scenario C and D |
vivo |
| R2-2502456 |
Service continuity discussion |
Qualcomm Incorporated |
| R2-2502611 |
Discussion on service continuity for Multi-hop Relay |
Huawei, HiSilicon |
| R2-2502626 |
Service Continuity for U2N multihop relay |
Kyocera |
| R2-2502675 |
Service Continuity for Multi-Hop Relays |
Ericsson |
| R2-2502694 |
Discussion on service continuity for multi-hop U2N relay |
LG Electronics Inc. |
| 8.14 |
Additional topological enhancements |
|
| R2-2501725 |
Reply LS on Support of UE move between CAG cell of 5G Femto and CSG cell (R3-244830; contact: Ericsson) |
RAN3 |
| R2-2501732 |
Reply LS on FS_VMR_Ph2 solution impacts to RAN (Additional ULI) (R3-250901; contact: ZTE) |
RAN3 |
| R2-2501733 |
Reply LS on Support of Location Service Involving WAB-Nodes (R3-250902; contact: Huawei) |
RAN3 |
| R2-2501749 |
Reply LS on Clarification regarding definition of 5G NR femto ownership (S2-2411241; contact: LGE) |
SA2 |
| R2-2501750 |
Reply LS on FS_VMR_Ph2 solution impacts to RAN (Access Control and Additional ULI) (S2-2501324; contact: Ericsson) |
SA2 |
| R2-2501751 |
Reply LS on FS_VMR_Ph2 solution impacts to RAN (MWAB mobility) (S2-2501336; contact: Nokia) |
SA2 |
| R2-2501755 |
LS on NR Femto node shared by PLMN and PNI-NPN (S2-2502787; contact: LGE) |
SA2 |
| 8.17 |
IoT-NTN TDD mode |
|
| R2-2501780 |
Discussion on RAN2 Imapcts of IoT-NTN TDD mode |
vivo |
| R2-2501970 |
Discussion on RAN2 impacts of IoT-NTN TDD |
Huawei, HiSilicon |
| R2-2501988 |
Work plan for WID: introduction of IoT-NTN TDD mode |
Iridium Satellite LLC |
| R2-2501989 |
Discussion on IoT-NTN TDD mode |
Iridium Satellite LLC |
| R2-2502059 |
Discussion on support of NB-IoT NTN TDD |
CATT |
| R2-2502071 |
Discussion on IoT NTN TDD mode |
OPPO |
| R2-2502100 |
Discussion on support of TDD mode for IoT-NTN |
Nokia, Nokia Shanghai Bell |
| R2-2502193 |
Discussion on support of IoT-NTN TDD mode |
THALES |
| R2-2502358 |
Discussion on TDD support in IoT NTN |
Lenovo |
| R2-2502459 |
On RAN2 aspect of IoT NTN TDD |
Samsung |
| R2-2502517 |
Discussion on supporting IoT NTN TDD mode |
Apple |
| R2-2502527 |
Consideration on IoT-NTN TDD mode |
ZTE Corporation, Sanechips |
| R2-2502538 |
Discussion on the IoT NTN TDD mode |
Xiaomi |
| R2-2502560 |
On SI scheduling, H-SFN change and postponing impacts in IoT-NTN TDD mode |
Nordic Semiconductor ASA |
| R2-2502621 |
Indication of IoT-NTN TDD Mode Support |
Toyota ITC |
| R2-2502658 |
Discussion on new NB-IoT NTN TDD mode |
Qualcomm Incorporated |
| R2-2502703 |
Support of IoT-NTN TDD mode |
CMCC |
| 8.18 |
TEI19 |
|
| R2-2501714 |
LS on non-RedCap UE UL SRS frequency hopping for positioning (R1-2501573; contact: ZTE) |
RAN1 |
| R2-2501781 |
Introduction of LTE TN to NB-IoT NTN Mobility UE Capability |
vivo, Samsung, Google, THALES, MediaTek Inc. |
| R2-2501869 |
Handling downlink BWP restriction for MT-SDT |
Samsung |
| R2-2501971 |
ETWS geo-fencing for eMTC NTN and for TN |
Huawei, HiSilicon, China Southern Power Grid, Turkcell |
| R2-2501991 |
BWP restriction in MT-SDT |
LG Electronics Inc. |
| R2-2502074 |
Introduction of control parameters for on-demand posSIB request [PosOdSIB-Req] |
Huawei, HiSilicon, Ericsson |
| R2-2502075 |
Introduction of control parameters for on-demand posSIB request [PosOdSIB-Req] |
Huawei, HiSilicon, Ericsson |
| R2-2502076 |
Introduction of control parameters for on-demand posSIB request [PosOdSIB-Req] |
Huawei, HiSilicon, Ericsson |
| R2-2502077 |
Introduction of control parameters for on-demand posSIB request [PosOdSIB-Req] |
Huawei, HiSilicon, Ericsson |
| R2-2502085 |
Discussion on the higher layer spec impact of positioning SRS FH for non-RedCap UE |
ZTE Corporation |
| R2-2502086 |
Introduction of the positioning SRS FH for non-RedCap UE in 38305 |
ZTE Corporation, Ericsson |
| R2-2502087 |
Introduction on the SRS frequency hopping for non-RedCap UE in 38331 [PosSrsFH-nonRedCap] |
ZTE Corporation, Ericsson |
| R2-2502209 |
SDT on separate BWP |
ZTE Corporation, Sanechips |
| R2-2502214 |
Addition of band specific number of Rx branches supported by a UE |
Nokia |
| R2-2502260 |
Draft reply LS on the non-RedCap UE UL SRS frequency hopping for positioning |
ZTE Corporation |
| R2-2502403 |
BWP restriction for SDT |
NEC |
| R2-2502498 |
Removing initial DL BWP restriction for MT-SDT |
Sony |
| R2-2502575 |
MPS at gNB overload |
Ericsson |
| R2-2502576 |
UE Radio Paging Capability |
Ericsson |
| R2-2502616 |
Discussion on simultaneous RAN and CN paging |
Nokia |
| R2-2502619 |
Simultaneous RAN and CN paging |
Nokia |
| R2-2502672 |
Discussion on RAN impact of UE usage of RAT restrictions |
Philips International B.V., NEC |
| R2-2502689 |
Redirection to IoT NTN and NR NTN |
Samsung |
| R2-2502734 |
Discussion on UE aggregation enhancement |
CMCC, ZTE, MediaTek, vivo, Huawei, CATT, Meta, Nokia, Nokia Shanghai Bell, xiaomi, Spreadtrum, UNISOC |
| R2-2502735 |
Corrections to TS 38.300 on multi-path relay enhancement |
CMCC, ZTE, MediaTek, vivo, Huawei, CATT, Meta, Nokia, Nokia Shanghai Bell, xiaomi, Spreadtrum, UNISOC |
| R2-2502736 |
Corrections to TS 38.331 on multi-path relay enhancement |
CMCC, ZTE, MediaTek, vivo, Huawei, CATT, Meta, Nokia, Nokia Shanghai Bell, xiaomi, Spreadtrum, UNISOC |
| R2-2502737 |
Corrections to TS 38.306 on multi-path relay enhancement |
CMCC, ZTE, MediaTek, vivo, Huawei, CATT, Meta, Nokia, Nokia Shanghai Bell, xiaomi, Spreadtrum, UNISOC |
| R2-2502783 |
Introduction of ANR reporting of HSDN cells [ANR_HSDN] |
Huawei, HiSilicon, CMCC, China Unicom, China Telecom, CATT, NTT DoCoMo, Samsung |
| R2-2502784 |
Introduction of ANR reporting of HSDN cells [ANR_HSDN] |
Huawei, HiSilicon, CMCC, China Unicom, China Telecom, CATT, NTT DoCoMo, Samsung |
| R2-2502785 |
Introduction of ANR reporting of HSDN cells [ANR_HSDN] |
Huawei, HiSilicon, CMCC, China Unicom, China Telecom, CATT, NTT DoCoMo, Samsung |
| R2-2502786 |
Introduction of ANR reporting of HSDN cells [ANR_HSDN] |
Huawei, HiSilicon, CMCC, China Unicom, China Telecom, CATT, NTT DoCoMo, Samsung |
| R2-2502803 |
36331CR for the inclusion of NB-IoT satellite information in E-UTRAN |
Google, Samsung, vivo, THALES |
| R2-2502804 |
36300CR for the inclusion of NB-IoT satellite information in E-UTRAN |
Google, Samsung, vivo, THALES |
| R2-2502914 |
Discussion on RNA update for MPS [MPS_RNAU_ResumeCause] |
Nokia |
| R2-2502996 |
Introduction of ANR reporting of HSDN cells [ANR_HSDN] |
Huawei, HiSilicon, CMCC, China Unicom, China Telecom, CATT, NTT DoCoMo, Samsung |
| R2-2502997 |
Introduction of ANR reporting of HSDN cells [ANR_HSDN] |
Huawei, HiSilicon, CMCC, China Unicom, China Telecom, CATT, NTT DoCoMo, Samsung |
| R2-2503151 |
Discussion on UE aggregation enhancement [N3C-M-Relay Ues] |
CMCC, ZTE, MediaTek, vivo, Huawei, CATT, Meta, Nokia, Nokia Shanghai Bell, xiaomi, Spreadtrum, UNISOC |
| R2-2503152 |
Corrections to TS 38.300 on multi-path relay enhancement [N3C-M-Relay Ues] |
CMCC, ZTE, MediaTek, vivo, Huawei, CATT, Meta, Nokia, Nokia Shanghai Bell, xiaomi, Spreadtrum, UNISOC |
| R2-2503153 |
Corrections to TS 38.331 on multi-path relay enhancement [N3C-M-Relay Ues] |
CMCC, ZTE, MediaTek, vivo, Huawei, CATT, Meta, Nokia, Nokia Shanghai Bell, xiaomi, Spreadtrum, UNISOC |
| R2-2503156 |
Corrections to TS 38.306 on multi-path relay enhancement [N3C-M-Relay UEs] |
CMCC, ZTE, MediaTek, vivo, Huawei, CATT, Meta, Nokia, Nokia Shanghai Bell, xiaomi, Spreadtrum, UNISOC |
| R2-2503157 |
Introduction of control parameters for on-demand posSIB request [PosOdSIB-Req] |
Huawei, HiSilicon, Ericsson |
| R2-2503158 |
Introduction of control parameters for on-demand posSIB request [PosOdSIB-Req] |
Huawei, HiSilicon, Ericsson |
| R2-2503159 |
Introduction of control parameters for on-demand posSIB request [PosOdSIB-Req] |
Huawei, HiSilicon, Ericsson |
| R2-2503160 |
Introduction of control parameters for on-demand posSIB request [PosOdSIB-Req] |
Huawei, HiSilicon, Ericsson |
| R2-2503172 |
Reply LS on paging capability loss issue |
RAN2 |
| R2-2503185 |
Reply LS on non-RedCap UE UL SRS frequency hopping for positioning |
RAN2 |
| 8.19 |
NR Others |
|
| R2-2501718 |
Reply LS on Ku band numerology (R1-2501609; contact: Eutelsat) |
RAN1 |
| R2-2501739 |
LS on CSSF optimization for NR RRM Phase 5 (R4-2502662; contact: Apple) |
RAN4 |
| R2-2501742 |
LS on switching periods for low-low band switching (R4-2502877; contact: AT&T) |
RAN4 |
| R2-2501744 |
LS on Signalling for 7 MHz Channel Bandwidth (R4-2503017; contact: T-Mobile) |
RAN4 |
| R2-2501758 |
Reply to RAN2 LS on Number of UEs in RRC_INACTIVE state with data transmission (S5-250827; contact: China Telecom) |
SA5 |
| R2-2501760 |
LS on Vendor Specific Trace Record (S5-251089; contact: Ericsson) |
SA5 |
| R2-2501910 |
Discussion on the number of SDT UEs (LS S5-250827) |
CATT |
| R2-2501911 |
Discussion on signalling for 7 MHz Channel Bandwidth (LS R4-2503017) |
CATT |
| R2-2501972 |
Discussion on CSSF optimization for NR RRM Phase 5 |
vivo |
| R2-2502248 |
Introduction of number of UEs in RRC_INACTIVE state with data transmission [KPI_SDT_SA5] |
China Telecom, Huawei, HiSilicon, ZTE Corporation, Sanechips, CATT |
| R2-2502313 |
RAN2 impact on CSSF optimization |
Apple, Ericsson, CATT |
| R2-2502569 |
Introduction of 7MHz channel bandwidth |
Ericsson, T-Mobile |
| R2-2502570 |
Introduction of 7MHz channel bandwidth |
Ericsson, T-Mobile |
| R2-2502571 |
Introduction of 7MHz channel bandwidth |
Ericsson, T-Mobile |
| R2-2502572 |
Introduction of 7MHz channel bandwidth |
Ericsson, T-Mobile |
| R2-2502635 |
Discussion on 7MHz bandwidth capabilities |
Nokia |
| R2-2502809 |
RAN2 impacts for 7 MHz Channel Bandwidth |
Huawei, HiSilicon |
| R2-2502869 |
Consideration on Supporting 7M Channel Bandwidth |
ZTE Corporation |
| R2-2503035 |
Introduction of number of UEs in RRC_INACTIVE state with data transmission [KPI_SDT_SA5] |
China Telecom, Huawei, HiSilicon, ZTE Corporation, Sanechips, CATT |
| R2-2503181 |
Reply LS on Number of UEs in RRC_INACTIVE state with data transmission |
RAN2 |
| R2-2503183 |
Reply LS on Signalling for 7 MHz Channel Bandwidth |
RAN2 |
| 9.1 |
Session on V2X/SL, R19 NES and MOB |
|
| R2-2502981 |
Report from session on V2X/SL, R19 NES and MOB |
Vice Chairman (Samsung) |
| 9.2 |
Session on R18 MIMOevo, R18 MUSIM, and R19 LP-WUS |
|
| R2-2502982 |
Rel-18 MIMO, Rel-19 MIMO, LPWUS, and SBFD |
Vice Chairman (CATT) |
| 9.3 |
Session on NR NTN and IoT NTN |
|
| R2-2502983 |
Report from session on NR NTN and IoT NTN |
Session chair (ZTE) |
| 9.4 |
Session on positioning and sidelink relay |
|
| R2-2502984 |
Report from session on positioning and sidelink relay |
Session chair (MediaTek) |
| 9.5 |
Session on R19 XR |
|
| R2-2502985 |
Report from session on R18 MBS, R18 QoE and R19 XR |
Session chair (Huawei) |
| 9.6 |
Session on maintenance and SON/MDT |
|
| R2-2502986 |
Report from session on maintenance and SON/MDT |
Session chair (Ericsson) |